bgpreport

Network · data from 2026-11-12

AS55379 hosei-net - Hosei University

Registry name: hosei-net - Hosei University, JP · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 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
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS55379, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55379, 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.25.0.0/16 No ROA Other IRR onlyJPIRR, RADB 672 100% 69
133.25.0.0/17 No ROA Other IRR onlyJPIRR, RADB 672 100% 69
133.25.128.0/17 No ROA Other IRR onlyJPIRR, RADB 672 100% 69
2001:df3:6500::/48 No ROA Other IRR onlyJPIRR, RADB 634 100% 69
2001:df3:6500::/49 No ROA Other IRR onlyJPIRR, RADB 18 3%low visibility 19
2001:df3:6500:8000::/49 No ROA Other IRR onlyJPIRR, RADB 18 3%low visibility 19

AS-SET

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

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none133.25.0.0/16No ROA covers it. Add a ROA for AS55379, maxLength 16.672 of 673
Route object: RIR133.25.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none133.25.0.0/17No ROA covers it. Add a ROA for AS55379, maxLength 17.672 of 673
Route object: RIR133.25.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none133.25.128.0/17No ROA covers it. Add a ROA for AS55379, maxLength 17.672 of 673
Route object: RIR133.25.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2001:df3:6500::/48No ROA covers it. Add a ROA for AS55379, maxLength 48.634 of 636
Route object: RIR2001:df3:6500::/48Route object only in JPIRR, RADB. Add it in the RIR database for the space.634 of 636
ROA: none2001:df3:6500::/49No ROA covers it. Add a ROA for AS55379, maxLength 49.18 of 636
Route object: RIR2001:df3:6500::/49Route object only in JPIRR, RADB. Add it in the RIR database for the space.18 of 636
ROA: none2001:df3:6500:8000::/49No ROA covers it. Add a ROA for AS55379, maxLength 49.18 of 636
Route object: RIR2001:df3:6500:8000::/49Route object only in JPIRR, RADB. Add it in the RIR database for the space.18 of 636

Route objects not announced

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

133.25.0.0/22JPIRR, RADBNo ROA
133.25.0.0/24RADBNo 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.