bgpreport

Network · data from 2026-11-12

AS18402 NLB-AS-SG-AP - NATIONAL LIBRARY BOARD

Registry name: NLB-AS-SG-AP - NATIONAL LIBRARY BOARD, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18402, 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.
203.78.12.0/24 No ROA Other origin only 670 100% 67
203.78.14.0/24 No ROA Other origin only 670 100% 67
203.78.15.0/24 No ROA Other origin only 670 100% 67
2001:df0:301::/48 No ROA None 632 99% 68
203.78.11.0/24 No ROA Other origin only 2 0%low visibility 2
203.78.13.0/24 No ROA Other origin only 2 0%low visibility 2
203.78.9.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66

AS-SET

AS18402 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none203.78.12.0/24No ROA covers it. Add a ROA for AS18402, maxLength 24.670 of 673
Route object: none203.78.12.0/24Route objects for it name AS4628. Add a route object with origin AS18402 in the RIR database for the space.670 of 673
ROA: none203.78.14.0/24No ROA covers it. Add a ROA for AS18402, maxLength 24.670 of 673
Route object: none203.78.14.0/24Route objects for it name AS4628. Add a route object with origin AS18402 in the RIR database for the space.670 of 673
ROA: none203.78.15.0/24No ROA covers it. Add a ROA for AS18402, maxLength 24.670 of 673
Route object: none203.78.15.0/24Route objects for it name AS4628. Add a route object with origin AS18402 in the RIR database for the space.670 of 673
ROA: none2001:df0:301::/48No ROA covers it. Add a ROA for AS18402, maxLength 48.632 of 636
Route object: none2001:df0:301::/48No route object for it. Add a route object with origin AS18402 in the RIR database for the space.632 of 636
ROA: none203.78.11.0/24No ROA covers it. Add a ROA for AS18402, maxLength 24.2 of 673
Route object: none203.78.11.0/24Route objects for it name AS4628. Add a route object with origin AS18402 in the RIR database for the space.2 of 673
ROA: none203.78.13.0/24No ROA covers it. Add a ROA for AS18402, maxLength 24.2 of 673
Route object: none203.78.13.0/24Route objects for it name AS4628. Add a route object with origin AS18402 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS18402 is announced.

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.