Network · data from 2026-11-12
AS7509 HINES - Hokkaido University
Registry name: HINES - Hokkaido University, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7509, 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.50.0.0/16 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 133.87.0.0/16 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 192.50.101.0/24 | No ROA | Other IRR onlyJPIRR | 670 100% |
AS-SET
AS7509 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: none3
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 133.50.0.0/16 | No ROA covers it. Add a ROA for AS7509, maxLength 16. |
| Route object: RIR | 133.50.0.0/16 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 133.87.0.0/16 | No ROA covers it. Add a ROA for AS7509, maxLength 16. |
| Route object: RIR | 133.87.0.0/16 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 192.50.101.0/24 | No ROA covers it. Add a ROA for AS7509, maxLength 24. |
| Route object: RIR | 192.50.101.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7509 whose prefix no peer sees AS7509 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.209.85.0/24 | JPIRR | Invalid: origin |
| 210.137.44.0/22 | JPIRR | Invalid: origin |
| 210.137.82.0/24 | JPIRR | Invalid: origin |
| 210.137.144.0/21 | JPIRR | Invalid: origin |
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.