Network · data from 2026-11-12
AS59104 SOKAU-AS - Soka University
Registry name: SOKAU-AS - Soka University, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59104, 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.
| 150.37.0.0/17 | No ROA | Nonecovered by 150.37.0.0/16 | 653 97% |
| 150.37.128.0/17 | No ROA | Nonecovered by 150.37.0.0/16 | 653 97% |
| 150.37.0.0/16 | No ROA | Other IRR onlyJPIRR | 673 100% |
AS-SET
AS59104 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 6 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 150.37.0.0/17 | No ROA covers it. Add a ROA for AS59104, maxLength 17. |
| Route object: none | 150.37.0.0/17 | No route object for it. A route object for 150.37.0.0/16 with origin AS59104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59104 in the RIR database for the space. |
| ROA: none | 150.37.128.0/17 | No ROA covers it. Add a ROA for AS59104, maxLength 17. |
| Route object: none | 150.37.128.0/17 | No route object for it. A route object for 150.37.0.0/16 with origin AS59104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59104 in the RIR database for the space. |
| ROA: none | 150.37.0.0/16 | No ROA covers it. Add a ROA for AS59104, maxLength 16. |
| Route object: RIR | 150.37.0.0/16 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS59104 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.