Network · data from 2026-11-12
AS46024 BNI-AS-ID - PT. Bank Negara Indonesia (Persero), Tbk.
Registry name: BNI-AS-ID - PT. Bank Negara Indonesia (Persero), Tbk., ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46024, 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.108.254.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.108.255.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.20.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.21.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.22.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.23.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.191.44.0/23 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS46024 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 19 are in fix.csv.
- ROA: none7
- Route object: RIR6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.108.254.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 103.108.254.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.108.255.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 103.108.255.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.106.20.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 175.106.20.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.106.21.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 175.106.21.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.106.22.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 175.106.22.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.106.23.0/24 | No ROA covers it. Add a ROA for AS46024, maxLength 24. |
| Route object: RIR | 175.106.23.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.191.44.0/23 | No ROA covers it. Add a ROA for AS46024, maxLength 23. |
Route objects not announced
Route objects with origin AS46024 whose prefix no peer sees AS46024 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.108.254.0/23 | RADB | No ROA |
| 175.106.20.0/22 | NTTCOM, RADB | No ROA |
| 175.106.20.0/23 | NTTCOM, RADB | No ROA |
| 175.106.22.0/23 | NTTCOM, RADB | No ROA |
| 203.191.44.0/24 | RADB | Valid |
| 203.191.45.0/24 | 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.