bgpreport

Network · data from 2026-11-12

AS56256 PERPUSNAS-AS-ID - Perpustakaan Nasional RI

Registry name: PERPUSNAS-AS-ID - Perpustakaan Nasional RI, ID · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS56256, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56256, 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.
2001:df5:3a00::/48 No ROA RIR databaseAPNIC, RADB 635 100% 70
103.28.21.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.41.109.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69

AS-SET

AS56256 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 14 are in fix.csv.

  • ROA: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none2001:df5:3a00::/48No ROA covers it. Add a ROA for AS56256, maxLength 48.635 of 636

Route objects not announced

Route objects with origin AS56256 whose prefix no peer sees AS56256 announce. Many are kept on purpose (backup routes, space announced only in some places).

223.27.144.0/20NTTCOMNo ROA
223.27.144.0/21NTTCOMNo ROA
223.27.144.0/22NTTCOMNo ROA
223.27.144.0/23NTTCOMNo ROA
223.27.146.0/23NTTCOMNo ROA
223.27.148.0/22NTTCOMNo ROA
223.27.148.0/23NTTCOMNo ROA
223.27.152.0/21NTTCOMNo ROA
223.27.152.0/22NTTCOMNo ROA
223.27.152.0/23NTTCOMNo ROA
223.27.156.0/22NTTCOMNo ROA
223.27.156.0/23NTTCOMNo ROA
223.27.158.0/23NTTCOMNo 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.