Network · data from 2026-11-12

AS17932 JAIST - Japan Advanced Institute of Science and Technology

Registry name: JAIST - Japan Advanced Institute of Science and Technology, JP · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object

2IPv6 routes 0.0% RPKI valid · 50.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

3No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS17932, seen from no peer

Announced routes

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


2001:200:141::/48	Invalid: origin	None	1 0%low visibility	2
192.50.109.0/24	No ROA	Other IRR onlyJPIRR, RADB	671 100%	67
150.65.0.0/16	No ROA	Other IRR onlyJPIRR, RADB	670 100%	69
2001:df0:2ed::/48	No ROA	Other IRR onlyJPIRR	633 100%	69

2001:200:141::/48

Invalid: origin

None

1 0%low visibility

192.50.109.0/24

No ROA

Other IRR onlyJPIRR, RADB

671 100%

150.65.0.0/16

No ROA

Other IRR onlyJPIRR, RADB

670 100%

2001:df0:2ed::/48

No ROA

Other IRR onlyJPIRR

633 100%

AS-SET

AS17932 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 8 are in fix.csv.

ROA: origin1
ROA: none3
Route object: none1
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2001:200:141::/48	ROAs covering it name AS2500, not AS17932. If AS17932 should announce it, add a ROA for AS17932.	1 of 636
Route object: none	2001:200:141::/48	No route object for it. Add a route object with origin AS17932 in the RIR database for the space.	1 of 636
ROA: none	192.50.109.0/24	No ROA covers it. Add a ROA for AS17932, maxLength 24.	671 of 673
Route object: RIR	192.50.109.0/24	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	150.65.0.0/16	No ROA covers it. Add a ROA for AS17932, maxLength 16.	670 of 673
Route object: RIR	150.65.0.0/16	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	2001:df0:2ed::/48	No ROA covers it. Add a ROA for AS17932, maxLength 48.	633 of 636
Route object: RIR	2001:df0:2ed::/48	Route object only in JPIRR. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2001:200:141::/48

ROAs covering it name AS2500, not AS17932. If AS17932 should announce it, add a ROA for AS17932.

1 of 636

Route object: none

2001:200:141::/48

No route object for it. Add a route object with origin AS17932 in the RIR database for the space.

1 of 636

ROA: none

192.50.109.0/24

No ROA covers it. Add a ROA for AS17932, maxLength 24.

671 of 673

Route object: RIR

192.50.109.0/24

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

671 of 673

ROA: none

150.65.0.0/16

No ROA covers it. Add a ROA for AS17932, maxLength 16.

670 of 673

Route object: RIR

150.65.0.0/16

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

670 of 673

ROA: none

2001:df0:2ed::/48

No ROA covers it. Add a ROA for AS17932, maxLength 48.

633 of 636

Route object: RIR

2001:df0:2ed::/48

Route object only in JPIRR. Add it in the RIR database for the space.

633 of 636

Route objects not announced

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