Network · data from 2026-11-12
AS154197 PT Reload Media Telematika
Registry name: IDNIC-LUMAJANGNETWORK-AS-ID - PT Reload Media Telematika, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154197, 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.
| 31.58.231.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 45.126.248.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.126.249.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS154197'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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 31.58.231.0/24 | ROAs covering it name AS834, not AS154197. If AS154197 should announce it, add a ROA for AS154197. |
| Route object: none | 31.58.231.0/24 | Route objects for it name AS834. Add a route object with origin AS154197 in the RIR database for the space. |
| Route object: RIR | 45.126.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.126.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154197 whose prefix no peer sees AS154197 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.126.248.0/23 | RADB | Valid |
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.