bgpreport

Network · data from 2026-11-12

AS17944 JWA - Japan Weather Association

Registry name: JWA - Japan Weather Association, JP · not in PeeringDB

5IPv4 routes 0.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
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS17944, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17944, 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.
133.105.0.0/16 No ROA Other IRR onlyJPIRR 672 100% 69
133.105.0.0/17 No ROA Other IRR onlyJPIRR 671 100% 69
133.105.128.0/17 No ROA Other IRR onlyJPIRR 671 100% 69
133.105.160.0/23 No ROA Other IRR onlyJPIRR 670 100% 67
192.51.39.0/24 No ROA Other IRR onlyJPIRR 669 99% 69
2001:df0:2ca::/48 No ROA Other IRR onlyJPIRR 634 100% 69

AS-SET

AS17944 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 15 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none133.105.0.0/16No ROA covers it. Add a ROA for AS17944, maxLength 16.672 of 673
Route object: RIR133.105.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none133.105.0.0/17No ROA covers it. Add a ROA for AS17944, maxLength 17.671 of 673
Route object: RIR133.105.0.0/17Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
ROA: none133.105.128.0/17No ROA covers it. Add a ROA for AS17944, maxLength 17.671 of 673
Route object: RIR133.105.128.0/17Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
ROA: none133.105.160.0/23No ROA covers it. Add a ROA for AS17944, maxLength 23.670 of 673
Route object: RIR133.105.160.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none192.51.39.0/24No ROA covers it. Add a ROA for AS17944, maxLength 24.669 of 673
Route object: RIR192.51.39.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none2001:df0:2ca::/48No ROA covers it. Add a ROA for AS17944, maxLength 48.634 of 636
Route object: RIR2001:df0:2ca::/48Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

133.105.0.0/24RADBNo ROA
192.51.39.0/25JPIRRNo ROA
192.51.39.128/25JPIRRNo 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.