Network · data from 2026-11-12
AS4855 PI-ID-AS-AP - Pacific Link Indonesia
Registry name: PI-ID-AS-AP - Pacific Link Indonesia, ID · not in PeeringDB
3IPv4 routes
0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
3No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
87Route objects not announced
registered with origin AS4855, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS4855, 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.
| 203.123.224.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.123.224.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.123.225.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS4855 isn't in PeeringDB, where networks name their AS-SET.
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 93 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced87
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.123.224.0/23 | No ROA covers it. Add a ROA for AS4855, maxLength 23. |
| Route object: RIR | 203.123.224.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.123.224.0/24 | No ROA covers it. Add a ROA for AS4855, maxLength 24. |
| Route object: RIR | 203.123.224.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.123.225.0/24 | No ROA covers it. Add a ROA for AS4855, maxLength 24. |
| Route object: RIR | 203.123.225.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4855 whose prefix no peer sees AS4855 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.123.224.0/24 | NTTCOM, RADB | No ROA |
| 202.123.225.0/24 | NTTCOM, RADB | No ROA |
| 202.123.226.0/24 | NTTCOM, RADB | No ROA |
| 202.123.227.0/24 | NTTCOM, RADB | No ROA |
| 202.123.228.0/24 | NTTCOM, RADB | No ROA |
| 202.123.229.0/24 | NTTCOM, RADB | No ROA |
| 202.123.230.0/24 | NTTCOM, RADB | No ROA |
| 202.123.231.0/24 | NTTCOM, RADB | No ROA |
| 202.123.232.0/24 | NTTCOM, RADB | No ROA |
| 202.123.233.0/24 | NTTCOM, RADB | No ROA |
| 202.123.234.0/24 | NTTCOM, RADB | No ROA |
| 202.123.235.0/24 | NTTCOM, RADB | No ROA |
| 202.123.236.0/24 | NTTCOM, RADB | No ROA |
| 202.123.237.0/24 | NTTCOM, RADB | No ROA |
| 202.123.238.0/24 | NTTCOM, RADB | No ROA |
| 202.123.239.0/24 | NTTCOM, RADB | No ROA |
| 202.123.241.0/24 | NTTCOM, RADB | No ROA |
| 202.123.247.0/24 | NTTCOM, RADB | No ROA |
| 202.123.248.0/24 | NTTCOM, RADB | No ROA |
| 202.123.249.0/24 | NTTCOM, RADB | No ROA |
| 202.123.250.0/24 | NTTCOM, RADB | No ROA |
| 202.123.251.0/24 | NTTCOM, RADB | No ROA |
| 202.123.252.0/24 | NTTCOM, RADB | No ROA |
| 202.123.253.0/24 | NTTCOM, RADB | No ROA |
| 202.123.254.0/24 | NTTCOM, RADB | No ROA |
| 202.123.255.0/24 | NTTCOM, RADB | No ROA |
| 203.123.224.0/19 | APNIC, NTTCOM, RADB | No ROA |
| 203.123.224.0/20 | NTTCOM, RADB | No ROA |
| 203.123.224.0/21 | NTTCOM, RADB | No ROA |
| 203.123.224.0/22 | NTTCOM, RADB | No ROA |
| 203.123.226.0/23 | NTTCOM, RADB | No ROA |
| 203.123.226.0/24 | NTTCOM, RADB | No ROA |
| 203.123.227.0/24 | NTTCOM, RADB | No ROA |
| 203.123.228.0/22 | NTTCOM, RADB | No ROA |
| 203.123.228.0/23 | NTTCOM, RADB | No ROA |
| 203.123.228.0/24 | NTTCOM, RADB | No ROA |
| 203.123.229.0/24 | NTTCOM, RADB | No ROA |
| 203.123.230.0/23 | NTTCOM, RADB | No ROA |
| 203.123.230.0/24 | NTTCOM, RADB | No ROA |
| 203.123.231.0/24 | NTTCOM, RADB | No ROA |
| 203.123.232.0/21 | NTTCOM, RADB | No ROA |
| 203.123.232.0/22 | NTTCOM, RADB | No ROA |
| 203.123.232.0/23 | NTTCOM, RADB | No ROA |
| 203.123.232.0/24 | NTTCOM, RADB | No ROA |
| 203.123.233.0/24 | NTTCOM, RADB | No ROA |
| 203.123.234.0/23 | NTTCOM, RADB | No ROA |
| 203.123.234.0/24 | NTTCOM, RADB | No ROA |
| 203.123.235.0/24 | NTTCOM, RADB | No ROA |
| 203.123.236.0/22 | NTTCOM, RADB | No ROA |
| 203.123.236.0/23 | NTTCOM, RADB | No ROA |
| 203.123.236.0/24 | NTTCOM, RADB | No ROA |
| 203.123.237.0/24 | NTTCOM, RADB | No ROA |
| 203.123.238.0/23 | NTTCOM, RADB | No ROA |
| 203.123.238.0/24 | NTTCOM, RADB | No ROA |
| 203.123.239.0/24 | NTTCOM, RADB | No ROA |
| 203.123.240.0/20 | NTTCOM, RADB | No ROA |
| 203.123.240.0/21 | NTTCOM, RADB | No ROA |
| 203.123.240.0/22 | NTTCOM, RADB | No ROA |
| 203.123.240.0/23 | NTTCOM, RADB | No ROA |
| 203.123.240.0/24 | NTTCOM, RADB | No ROA |
| 203.123.241.0/24 | NTTCOM, RADB | No ROA |
| 203.123.242.0/23 | NTTCOM, RADB | No ROA |
| 203.123.242.0/24 | NTTCOM, RADB | No ROA |
| 203.123.243.0/24 | NTTCOM, RADB | No ROA |
| 203.123.244.0/22 | NTTCOM, RADB | No ROA |
| 203.123.244.0/23 | NTTCOM, RADB | No ROA |
| 203.123.244.0/24 | NTTCOM, RADB | No ROA |
| 203.123.245.0/24 | NTTCOM, RADB | No ROA |
| 203.123.246.0/23 | NTTCOM, RADB | No ROA |
| 203.123.246.0/24 | NTTCOM, RADB | No ROA |
| 203.123.247.0/24 | NTTCOM, RADB | No ROA |
| 203.123.248.0/21 | NTTCOM, RADB | No ROA |
| 203.123.248.0/22 | NTTCOM, RADB | No ROA |
| 203.123.248.0/23 | NTTCOM, RADB | No ROA |
| 203.123.248.0/24 | NTTCOM, RADB | No ROA |
| 203.123.249.0/24 | NTTCOM, RADB | No ROA |
| 203.123.250.0/23 | NTTCOM, RADB | No ROA |
| 203.123.250.0/24 | NTTCOM, RADB | No ROA |
| 203.123.251.0/24 | NTTCOM, RADB | No ROA |
| 203.123.252.0/22 | NTTCOM, RADB | No ROA |
| 203.123.252.0/23 | NTTCOM, RADB | No ROA |
| 203.123.252.0/24 | NTTCOM, RADB | No ROA |
| 203.123.253.0/24 | NTTCOM, RADB | No ROA |
| 203.123.254.0/23 | NTTCOM, RADB | No ROA |
| 203.123.254.0/24 | NTTCOM, RADB | No ROA |
| 203.123.255.0/24 | NTTCOM, RADB | No ROA |
| 203.153.49.0/24 | NTTCOM, 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.