Network · data from 2026-11-12
AS4622 IDNIC AS4622
Registry name: ID-NIC - Indonesia Network Information Center, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4622, 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.
| 2001:dc6:1::/48 | No ROA | Nonecovered by 2001:dc6::/32 | 635 100% |
| 2001:dc6:2::/48 | No ROA | Nonecovered by 2001:dc6::/32 | 635 100% |
| 2001:dc6:3::/48 | No ROA | Nonecovered by 2001:dc6::/32 | 635 100% |
| 2001:dc6:666::/48 | No ROA | Nonecovered by 2001:dc6::/32 | 635 100% |
| 103.88.88.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2001:dc6::/32 | No ROA | RIR databaseAPNIC, RADB | 3 0%low visibility |
| 2001:dc6::/48 | Valid | Nonecovered by 2001:dc6::/32 | 635 100% |
| 203.119.52.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.119.13.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.119.53.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.119.54.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 203.119.55.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS4622: AS-APJII-GLOBAL. 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 (AS4622 isn't in the set, or no route object for AS4622 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 | AS4622 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-APJII-GLOBAL | In no IRR database read today. | |||||
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: none6
- Route object: none5
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:dc6:1::/48 | No ROA covers it. Add a ROA for AS4622, maxLength 48. |
| Route object: none | 2001:dc6:1::/48 | No route object for it. A route object for 2001:dc6::/32 with origin AS4622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4622 in the RIR database for the space. |
| ROA: none | 2001:dc6:2::/48 | No ROA covers it. Add a ROA for AS4622, maxLength 48. |
| Route object: none | 2001:dc6:2::/48 | No route object for it. A route object for 2001:dc6::/32 with origin AS4622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4622 in the RIR database for the space. |
| ROA: none | 2001:dc6:3::/48 | No ROA covers it. Add a ROA for AS4622, maxLength 48. |
| Route object: none | 2001:dc6:3::/48 | No route object for it. A route object for 2001:dc6::/32 with origin AS4622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4622 in the RIR database for the space. |
| ROA: none | 2001:dc6:666::/48 | No ROA covers it. Add a ROA for AS4622, maxLength 48. |
| Route object: none | 2001:dc6:666::/48 | No route object for it. A route object for 2001:dc6::/32 with origin AS4622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4622 in the RIR database for the space. |
| ROA: none | 103.88.88.0/24 | No ROA covers it. Add a ROA for AS4622, maxLength 24. |
| Route object: RIR | 103.88.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:dc6::/32 | No ROA covers it. Add a ROA for AS4622, maxLength 32. |
| Route object: none | 2001:dc6::/48 | No route object for it. A route object for 2001:dc6::/32 with origin AS4622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4622 in the RIR database for the space. |
| Route object: RIR | 203.119.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-APJII-GLOBAL | PeeringDB names AS-APJII-GLOBAL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS4622 whose prefix no peer sees AS4622 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.123.20.0/22 | APNIC | No ROA |
| 103.123.20.0/24 | APNIC | No ROA |
| 103.123.21.0/24 | APNIC | No ROA |
| 103.123.22.0/24 | APNIC | No ROA |
| 103.123.23.0/24 | APNIC | No ROA |
| 203.119.41.0/24 | APNIC, NTTCOM | No ROA |
| 203.119.52.0/22 | NTTCOM | Valid |
| 203.119.52.0/23 | NTTCOM, RADB | Valid |
| 203.119.54.0/23 | APNIC, NTTCOM, RADB | Valid |
| 2001:7fa:2:100::/64 | RADB | No 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.