Network · data from 2026-11-12
AS48631 ODINE-AS Odine Solutions FZ-LLC
Registry name: ODINE-AS Odine Solutions FZ-LLC, AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48631, 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.
| 178.22.8.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.9.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.10.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.11.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.13.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.14.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 178.22.15.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 194.62.142.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 194.62.143.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 194.62.140.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 194.62.141.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 178.22.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 74.201.100.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 202.9.56.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.9.50.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 74.201.101.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
AS-SET
AS48631 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 13 are in fix.csv.
- Route object: RIR11
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 178.22.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.22.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.62.142.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.62.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.62.140.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.62.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48631 whose prefix no peer sees AS48631 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.22.8.0/21 | RIPE | No ROA |
| 194.62.140.0/22 | RIPE | 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.