Network · data from 2026-11-12
AS153135 IDNIC-NPN-AS-ID - PT Netindo Persada Nusantara
Registry name: IDNIC-NPN-AS-ID - PT Netindo Persada Nusantara, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS153135, 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.
| 162.4.44.0/24 | Invalid: origin | Other origin only | 35 5%low visibility |
| 144.79.37.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 160.187.174.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS153135 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 162.4.44.0/24 | ROAs covering it name AS154663, not AS153135. If AS153135 should announce it, add a ROA for AS153135. |
| Route object: none | 162.4.44.0/24 | Route objects for it name AS154663. Add a route object with origin AS153135 in the RIR database for the space. |
| Route object: RIR | 144.79.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.187.174.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS153135 whose prefix no peer sees AS153135 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df4:5d40::/48 | 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.