Network · data from 2026-11-12
AS17996 Global Prima Utama, PT
Registry name: UIINET-ID-AP - PT Global Prima Utama, ID · PeeringDB
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 |
| 202.52.156.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.162.46.0/23 | Valid | Nonecovered by 202.162.32.0/20 | 672 100% |
| 103.162.100.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 202.162.40.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 202.162.42.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 202.162.32.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.162.33.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.34.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.162.34.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.35.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.36.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.37.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.38.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.39.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.41.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.44.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.162.45.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 2402:a600::/32 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 636 100% |
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.
| Name | Database | ASNs | Sets | AS17996 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS17996:AS-UIINET | APNIC1 member set in no database: AS17996:AS-CUSTOMERS | 6 | 1 | 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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.162.32.17/32 | ROA 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. |
| Route object: none | 202.162.32.17/32 | No 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. |
| ROA: none | 202.52.156.0/24 | No ROA covers it. Add a ROA for AS17996, maxLength 24. |
| Route object: RIR | 202.52.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 202.162.46.0/23 | No 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. |
| Route object: RIR | 103.162.100.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.162.40.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.162.42.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | APNIC::AS17996:AS-UIINET | AS17996: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/24 | RADB | Valid |
| 202.162.32.0/20 | NTTCOM, RADB, REACH | Valid |
| 202.162.32.0/21 | RADB | Valid |
| 202.162.32.0/22 | RADB | Valid |
| 202.162.32.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 202.162.36.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.162.36.0/23 | RADB | Valid |
| 202.162.38.0/23 | RADB | Valid |
| 202.162.40.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.162.40.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 202.162.42.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 202.162.43.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 202.162.46.0/24 | APNIC, NTTCOM, REACH | Valid |
| 202.162.47.0/24 | APNIC, NTTCOM, REACH | Valid |
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.