Network · data from 2026-11-12
AS9366 SOLITON - SOLITON-NET
Registry name: SOLITON - SOLITON-NET, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9366, 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.
| 160.239.10.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.239.11.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.239.12.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.239.15.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.239.0.0/16 | No ROA | Other IRR onlyRADB | 671 100% |
| 160.239.1.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS9366 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 23 are in fix.csv.
- ROA: none6
- Route object: RIR6
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 160.239.10.0/24 | No ROA covers it. Add a ROA for AS9366, maxLength 24. |
| Route object: RIR | 160.239.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.239.11.0/24 | No ROA covers it. Add a ROA for AS9366, maxLength 24. |
| Route object: RIR | 160.239.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.239.12.0/24 | No ROA covers it. Add a ROA for AS9366, maxLength 24. |
| Route object: RIR | 160.239.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.239.15.0/24 | No ROA covers it. Add a ROA for AS9366, maxLength 24. |
| Route object: RIR | 160.239.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.239.0.0/16 | No ROA covers it. Add a ROA for AS9366, maxLength 16. |
| Route object: RIR | 160.239.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.239.1.0/24 | No ROA covers it. Add a ROA for AS9366, maxLength 24. |
| Route object: RIR | 160.239.1.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9366 whose prefix no peer sees AS9366 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.239.16.0/24 | RADB | No ROA |
| 160.239.17.0/24 | RADB | No ROA |
| 160.239.18.0/24 | RADB | No ROA |
| 160.239.20.0/24 | RADB | No ROA |
| 160.239.21.0/24 | RADB | No ROA |
| 160.239.30.0/24 | RADB | No ROA |
| 160.239.31.0/24 | RADB | No ROA |
| 160.239.32.0/24 | RADB | No ROA |
| 160.239.33.0/24 | RADB | No ROA |
| 160.239.34.0/24 | RADB | No ROA |
| 160.239.35.0/24 | RADB | No 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.