Network · data from 2026-11-19
AS139398 Pusat Informasi Kredit
Registry name: IDNIC-PIK-ID - PT. Pusat Informasi Kredit, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139398, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.
| 144.48.13.0/24 | Invalid: origin | None | 1 0%low visibility |
| 144.48.14.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS139398's PeeringDB record names no 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 144.48.13.0/24 | ROAs covering it name AS38496, not AS139398. If AS139398 should announce it, add a ROA for AS139398. |
| Route object: none | 144.48.13.0/24 | No route object for it. Add a route object with origin AS139398 in the RIR database for the space. |
| ROA: origin | 144.48.14.0/24 | ROAs covering it name AS38496, not AS139398. If AS139398 should announce it, add a ROA for AS139398. |
| Route object: none | 144.48.14.0/24 | No route object for it. Add a route object with origin AS139398 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS139398 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-19 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.