Network · data from 2026-11-12
AS136854 PRB-AS-ID - PT. PALAPA RING BARAT
Registry name: PRB-AS-ID - PT. PALAPA RING BARAT, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136854, 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.102.140.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.102.141.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.102.142.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.102.143.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
AS-SET
AS136854 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 6 are in fix.csv.
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.102.140.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.141.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.142.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.143.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS136854 whose prefix no peer sees AS136854 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.102.140.0/22 | APNIC | Valid |
| 2401:e440::/32 | NTTCOM | 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.