bgpreport

Network · data from 2026-11-12

AS17523 AOYAMA - Aoyama Gakuin University

Registry name: AOYAMA - Aoyama Gakuin University, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17523, 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:df7:7800::/49 No ROA Nonecovered by 2001:df7:7800::/48 16 3%low visibility 18
2001:df7:7800:8000::/49 No ROA Nonecovered by 2001:df7:7800::/48 16 3%low visibility 18
133.2.0.0/17 No ROA Other IRR onlyJPIRR 672 100% 69
133.2.128.0/17 No ROA Other IRR onlyJPIRR 672 100% 69

AS-SET

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

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:df7:7800::/49No ROA covers it. Add a ROA for AS17523, maxLength 49.16 of 636
Route object: none2001:df7:7800::/49No route object for it. A route object for 2001:df7:7800::/48 with origin AS17523 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS17523 in the RIR database for the space.16 of 636
ROA: none2001:df7:7800:8000::/49No ROA covers it. Add a ROA for AS17523, maxLength 49.16 of 636
Route object: none2001:df7:7800:8000::/49No route object for it. A route object for 2001:df7:7800::/48 with origin AS17523 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS17523 in the RIR database for the space.16 of 636
ROA: none133.2.0.0/17No ROA covers it. Add a ROA for AS17523, maxLength 17.672 of 673
Route object: RIR133.2.0.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none133.2.128.0/17No ROA covers it. Add a ROA for AS17523, maxLength 17.672 of 673
Route object: RIR133.2.128.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

133.2.0.0/16JPIRR, NTTCOM, RADBNo ROA
2001:df7:7800::/48JPIRRNo 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.