bgpreport

Network · data from 2026-11-12

AS2522 PPP-EXP - Japan Network Information Center

Registry name: PPP-EXP - Japan Network Information Center, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2522, 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.
61.122.16.0/22 No ROA Other IRR onlyJPIRR 673 100% 67
103.210.108.0/22 No ROA Other IRR onlyJPIRR 673 100% 67
133.112.0.0/16 No ROA Other IRR onlyJPIRR 673 100% 67
150.41.0.0/16 No ROA Other IRR onlyJPIRR 673 100% 67
158.200.0.0/16 No ROA Other IRR onlyJPIRR 673 100% 67
192.47.97.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
192.50.235.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
202.210.56.0/22 No ROA Other IRR onlyJPIRR 673 100% 67
203.179.64.0/20 No ROA Other IRR onlyJPIRR 673 100% 67
211.1.0.0/19 No ROA Other IRR onlyJPIRR 673 100% 67
219.101.112.0/20 No ROA Other IRR onlyJPIRR 673 100% 67
220.213.240.0/20 No ROA Other IRR onlyJPIRR 673 100% 67
210.134.208.0/20 No ROA Other IRR onlyJPIRR 672 100% 67
218.231.16.0/20 No ROA Other IRR onlyJPIRR 672 100% 67
203.178.8.0/24 No ROA Other IRR onlyJPIRR 670 100% 67

AS-SET

AS2522 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 31 are in fix.csv.

  • ROA: none15
  • Route object: RIR15
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none61.122.16.0/22No ROA covers it. Add a ROA for AS2522, maxLength 22.673 of 673
Route object: RIR61.122.16.0/22Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none103.210.108.0/22No ROA covers it. Add a ROA for AS2522, maxLength 22.673 of 673
Route object: RIR103.210.108.0/22Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none133.112.0.0/16No ROA covers it. Add a ROA for AS2522, maxLength 16.673 of 673
Route object: RIR133.112.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none150.41.0.0/16No ROA covers it. Add a ROA for AS2522, maxLength 16.673 of 673
Route object: RIR150.41.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none158.200.0.0/16No ROA covers it. Add a ROA for AS2522, maxLength 16.673 of 673
Route object: RIR158.200.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none192.47.97.0/24No ROA covers it. Add a ROA for AS2522, maxLength 24.673 of 673
Route object: RIR192.47.97.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none192.50.235.0/24No ROA covers it. Add a ROA for AS2522, maxLength 24.673 of 673
Route object: RIR192.50.235.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none202.210.56.0/22No ROA covers it. Add a ROA for AS2522, maxLength 22.673 of 673
Route object: RIR202.210.56.0/22Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none203.179.64.0/20No ROA covers it. Add a ROA for AS2522, maxLength 20.673 of 673
Route object: RIR203.179.64.0/20Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none211.1.0.0/19No ROA covers it. Add a ROA for AS2522, maxLength 19.673 of 673
Route object: RIR211.1.0.0/19Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none219.101.112.0/20No ROA covers it. Add a ROA for AS2522, maxLength 20.673 of 673
Route object: RIR219.101.112.0/20Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none220.213.240.0/20No ROA covers it. Add a ROA for AS2522, maxLength 20.673 of 673
Route object: RIR220.213.240.0/20Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none210.134.208.0/20No ROA covers it. Add a ROA for AS2522, maxLength 20.672 of 673
Route object: RIR210.134.208.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none218.231.16.0/20No ROA covers it. Add a ROA for AS2522, maxLength 20.672 of 673
Route object: RIR218.231.16.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none203.178.8.0/24No ROA covers it. Add a ROA for AS2522, maxLength 24.670 of 673
Route object: RIR203.178.8.0/24Route object only in JPIRR. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

202.13.72.0/24JPIRRNo 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.