bgpreport

Network · data from 2026-11-12

AS9367 ISCT - Institute of Science Tokyo

Registry name: ISCT - Institute of Science Tokyo, JP · not in PeeringDB

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

Announced routes

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

131.112.254.0/24 No ROA Nonecovered by 131.112.0.0/16 669 99% 69
131.112.0.0/16 No ROA Other IRR onlyJPIRR, RADB 672 100% 69
2403:4440::/32 No ROA Other IRR onlyJPIRR 634 100% 69

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none131.112.254.0/24No ROA covers it. Add a ROA for AS9367, maxLength 24.669 of 673
Route object: none131.112.254.0/24No route object for it. A route object for 131.112.0.0/16 with origin AS9367 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9367 in the RIR database for the space.669 of 673
ROA: none131.112.0.0/16No ROA covers it. Add a ROA for AS9367, maxLength 16.672 of 673
Route object: RIR131.112.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2403:4440::/32No ROA covers it. Add a ROA for AS9367, maxLength 32.634 of 636
Route object: RIR2403:4440::/32Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2001:200:136::/48APNICValid

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.