bgpreport

Network · data from 2026-11-12

AS131971 JPNIC-LAB

Registry name: AS131971-67 - JPNIC-4Byte-ASBLOCK-AP, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131971, 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.

2407:9900:1000::/36 Invalid: origin None 154 24% 57
202.1.213.0/24 Invalid: origin None 92 14% 44
202.1.214.0/24 No ROA None 672 100% 67
2407:9900:2000::/36 No ROA None 635 100% 68
202.1.208.0/22 Valid None 673 100% 67
202.1.212.0/24 Valid None 673 100% 67
202.1.215.0/24 Valid None 673 100% 67
2407:9900::/36 Valid None 635 100% 68
2407:9900:3000::/36 Valid None 635 100% 68
2407:9900:4000::/35 Valid None 635 100% 68
2407:9900:6000::/35 Valid None 635 100% 68
2407:9900:8000::/33 Valid None 635 100% 68

AS-SET

AS131971'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 17 are in fix.csv.

  • ROA: origin2
  • ROA: none2
  • Route object: none12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2407:9900:1000::/36ROAs covering it name AS2515, not AS131971. If AS131971 should announce it, add a ROA for AS131971.154 of 636
Route object: none2407:9900:1000::/36No route object for it. Add a route object with origin AS131971 in the RIR database for the space.154 of 636
ROA: origin202.1.213.0/24ROAs covering it name AS2515, not AS131971. If AS131971 should announce it, add a ROA for AS131971.92 of 673
Route object: none202.1.213.0/24No route object for it. Add a route object with origin AS131971 in the RIR database for the space.92 of 673
ROA: none202.1.214.0/24No ROA covers it. Add a ROA for AS131971, maxLength 24.672 of 673
Route object: none202.1.214.0/24No route object for it. Add a route object with origin AS131971 in the RIR database for the space.672 of 673
ROA: none2407:9900:2000::/36No ROA covers it. Add a ROA for AS131971, maxLength 36.635 of 636
Route object: none2407:9900:2000::/36No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636
Route object: none202.1.208.0/22No route object for it. Add a route object with origin AS131971 in the RIR database for the space.673 of 673
Route object: none202.1.212.0/24No route object for it. Add a route object with origin AS131971 in the RIR database for the space.673 of 673
Route object: none202.1.215.0/24No route object for it. Add a route object with origin AS131971 in the RIR database for the space.673 of 673
Route object: none2407:9900::/36No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636
Route object: none2407:9900:3000::/36No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636
Route object: none2407:9900:4000::/35No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636
Route object: none2407:9900:6000::/35No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636
Route object: none2407:9900:8000::/33No route object for it. Add a route object with origin AS131971 in the RIR database for the space.635 of 636

Route objects not announced

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

103.255.104.0/22RADBNo 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.