bgpreport

Network · data from 2026-11-12

AS18087 TOYO - Toyo University

Registry name: TOYO - Toyo University, JP · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 75.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS18087, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18087, 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.79.192.0/20 No ROA Nonecovered by 133.79.128.0/17 653 97% 69
133.79.0.0/16 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
133.79.0.0/17 No ROA Other IRR onlyJPIRR 672 100% 69
133.79.128.0/17 No ROA Other IRR onlyJPIRR 672 100% 69
2001:df7:5600::/48 No ROA Other IRR onlyJPIRR 634 100% 69
2001:df7:5600:8000::/52 No ROA Other IRR onlyJPIRR 15 2%low visibility 16

AS-SET

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none133.79.192.0/20No ROA covers it. Add a ROA for AS18087, maxLength 20.653 of 673
Route object: none133.79.192.0/20No route object for it. A route object for 133.79.128.0/17 with origin AS18087 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18087 in the RIR database for the space.653 of 673
ROA: none133.79.0.0/16No ROA covers it. Add a ROA for AS18087, maxLength 16.673 of 673
Route object: RIR133.79.0.0/16Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none133.79.0.0/17No ROA covers it. Add a ROA for AS18087, maxLength 17.672 of 673
Route object: RIR133.79.0.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none133.79.128.0/17No ROA covers it. Add a ROA for AS18087, maxLength 17.672 of 673
Route object: RIR133.79.128.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none2001:df7:5600::/48No ROA covers it. Add a ROA for AS18087, maxLength 48.634 of 636
Route object: RIR2001:df7:5600::/48Route object only in JPIRR. Add it in the RIR database for the space.634 of 636
ROA: none2001:df7:5600:8000::/52No ROA covers it. Add a ROA for AS18087, maxLength 52.15 of 636
Route object: RIR2001:df7:5600:8000::/52Route object only in JPIRR. Add it in the RIR database for the space.15 of 636

Route objects not announced

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