bgpreport

Network · data from 2026-11-12

AS17996 Global Prima Utama, PT

Registry name: UIINET-ID-AP - PT Global Prima Utama, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17996, 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.

202.162.32.17/32 Invalid: maxLength Nonecovered by 202.162.32.0/24 2 0%low visibility 3
202.52.156.0/24 No ROA Other IRR onlyRADB 673 100% 68
202.162.46.0/23 Valid Nonecovered by 202.162.32.0/20 672 100% 67
103.162.100.0/23 Valid Other IRR onlyRADB 672 100% 67
202.162.40.0/23 Valid Other IRR onlyRADB 672 100% 68
202.162.42.0/23 Valid Other IRR onlyRADB 672 100% 67
202.162.32.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.162.33.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.34.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.162.34.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.35.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.36.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.37.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.38.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.39.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.41.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 68
202.162.44.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
202.162.45.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
2402:a600::/32 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 70

AS-SET

PeeringDB's irr_as_set for AS17996: APNIC::AS17996:AS-UIINET. 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 (AS17996 isn't in the set, or no route object for AS17996 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 objectsAS17996 in itNot covered
APNIC::AS17996:AS-UIINET APNIC1 member set in no database: AS17996:AS-CUSTOMERS 6191 Yes 1

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 23 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none2
  • Route object: RIR4
  • AS-SET: missing member1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: maxLength202.162.32.17/32ROA 202.162.32.0/20 AS17996 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.162.32.17/32.2 of 673
Route object: none202.162.32.17/32No route object for it. A route object for 202.162.32.0/24 with origin AS17996 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS17996 in the RIR database for the space.2 of 673
ROA: none202.52.156.0/24No ROA covers it. Add a ROA for AS17996, maxLength 24.673 of 673
Route object: RIR202.52.156.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none202.162.46.0/23No route object for it. A route object for 202.162.32.0/20 with origin AS17996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17996 in the RIR database for the space.672 of 673
Route object: RIR103.162.100.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.162.40.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.162.42.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: missing memberAPNIC::AS17996:AS-UIINETAS17996:AS-UIINET (APNIC) lists AS17996:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

103.162.100.0/24RADBValid
202.162.32.0/20NTTCOM, RADB, REACHValid
202.162.32.0/21RADBValid
202.162.32.0/22RADBValid
202.162.32.0/24APNIC, NTTCOM, RADB, REACHValid
202.162.36.0/22APNIC, NTTCOM, RADBValid
202.162.36.0/23RADBValid
202.162.38.0/23RADBValid
202.162.40.0/22APNIC, NTTCOM, RADBValid
202.162.40.0/24APNIC, NTTCOM, RADB, REACHValid
202.162.42.0/24APNIC, NTTCOM, RADB, REACHValid
202.162.43.0/24APNIC, NTTCOM, RADB, REACHValid
202.162.46.0/24APNIC, NTTCOM, REACHValid
202.162.47.0/24APNIC, NTTCOM, REACHValid

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.