bgpreport

Network · data from 2026-11-12

AS59147 Drupadi Prima

Registry name: IDNIC-DRUPADI-AS-ID - PT. Drupadi Prima, ID · PeeringDB

13IPv4 routes 23.1% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
10No ROA 0 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS59147, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59147, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

103.52.144.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.52.145.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.52.146.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.52.147.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.84.192.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.84.193.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.84.194.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.84.195.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.52.144.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.84.192.0/22 No ROA RIR databaseAPNIC, RADB 672 100% 68
103.252.100.0/24 Valid Other IRR onlyNTTCOM 2 0%low visibility 2
103.252.101.0/24 Valid Other IRR onlyNTTCOM 2 0%low visibility 2
103.252.100.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 68

AS-SET

PeeringDB's irr_as_set for AS59147: IDNIC::AS59147. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS59147 isn't in the set, or no route object for AS59147 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS59147 in itNot covered
IDNIC::AS59147 A single AS number, not a set: AS59147 (this network), 17 route objects.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.52.144.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.52.144.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.52.145.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.52.145.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.52.146.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.52.146.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.52.147.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.52.147.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.84.192.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.84.192.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none103.84.193.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.84.193.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none103.84.194.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.84.194.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none103.84.195.0/24No ROA covers it. Add a ROA for AS59147, maxLength 24.2 of 673
Route object: RIR103.84.195.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none103.52.144.0/22No ROA covers it. Add a ROA for AS59147, maxLength 22.672 of 673
ROA: none103.84.192.0/22No ROA covers it. Add a ROA for AS59147, maxLength 22.672 of 673
Route object: RIR103.252.100.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
Route object: RIR103.252.101.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS59147 whose prefix no peer sees AS59147 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.52.144.0/23NTTCOMNo ROA
103.52.146.0/23NTTCOMNo ROA
103.84.192.0/23RADBNo ROA
103.84.194.0/23RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.