Network · data from 2026-11-12
AS18124 OUS-NET - Okayama University of Science
Registry name: OUS-NET - Okayama University of Science, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18124, 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.55.128.0/17 | No ROA | Nonecovered by 150.55.0.0/16 | 653 97% |
| 150.55.0.0/16 | No ROA | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 150.55.0.0/17 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.0.0/18 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.64.0/18 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.128.0/18 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.128.0/21 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.192.0/18 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 150.55.128.0/22 | No ROA | Other IRR onlyJPIRR | 670 100% |
| 150.55.132.0/22 | No ROA | Other IRR onlyJPIRR | 670 100% |
| 2001:df0:3d80::/48 | No ROA | Other IRR onlyJPIRR, RADB | 635 100% |
AS-SET
AS18124 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 22 are in fix.csv.
- ROA: none11
- Route object: none1
- Route object: RIR10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 150.55.128.0/17 | No ROA covers it. Add a ROA for AS18124, maxLength 17. |
| Route object: none | 150.55.128.0/17 | No route object for it. A route object for 150.55.0.0/16 with origin AS18124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18124 in the RIR database for the space. |
| ROA: none | 150.55.0.0/16 | No ROA covers it. Add a ROA for AS18124, maxLength 16. |
| Route object: RIR | 150.55.0.0/16 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 150.55.0.0/17 | No ROA covers it. Add a ROA for AS18124, maxLength 17. |
| Route object: RIR | 150.55.0.0/17 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.0.0/18 | No ROA covers it. Add a ROA for AS18124, maxLength 18. |
| Route object: RIR | 150.55.0.0/18 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.64.0/18 | No ROA covers it. Add a ROA for AS18124, maxLength 18. |
| Route object: RIR | 150.55.64.0/18 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.128.0/18 | No ROA covers it. Add a ROA for AS18124, maxLength 18. |
| Route object: RIR | 150.55.128.0/18 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.128.0/21 | No ROA covers it. Add a ROA for AS18124, maxLength 21. |
| Route object: RIR | 150.55.128.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.192.0/18 | No ROA covers it. Add a ROA for AS18124, maxLength 18. |
| Route object: RIR | 150.55.192.0/18 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.128.0/22 | No ROA covers it. Add a ROA for AS18124, maxLength 22. |
| Route object: RIR | 150.55.128.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 150.55.132.0/22 | No ROA covers it. Add a ROA for AS18124, maxLength 22. |
| Route object: RIR | 150.55.132.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 2001:df0:3d80::/48 | No ROA covers it. Add a ROA for AS18124, maxLength 48. |
| Route object: RIR | 2001:df0:3d80::/48 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS18124 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.