bgpreport

Network · data from 2026-11-12

AS17512 Japan Airlines

Registry name: JAL - Japan Airlines Co.,Ltd., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17512, 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.
163.211.0.0/16 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
163.211.0.0/17 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
163.211.128.0/17 No ROA Other IRR onlyJPIRR, RADB 672 100% 67

AS-SET

AS17512'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 6 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none163.211.0.0/16No ROA covers it. Add a ROA for AS17512, maxLength 16.672 of 673
Route object: RIR163.211.0.0/16Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.211.0.0/17No ROA covers it. Add a ROA for AS17512, maxLength 17.672 of 673
Route object: RIR163.211.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.211.128.0/17No ROA covers it. Add a ROA for AS17512, maxLength 17.672 of 673
Route object: RIR163.211.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS17512 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.