Network · data from 2026-11-12
AS9193 ConXionEU NAVISITE OPCO LLC
Registry name: ConXionEU NAVISITE OPCO LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9193, 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.
| 144.34.58.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 62.32.96.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 62.32.105.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.32.106.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.32.108.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.32.110.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.32.111.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 207.45.112.0/20 | No ROA | RIR databaseARIN, RIPE-NONAUTH | 673 100% |
| 213.35.4.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.10.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.33.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.34.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.37.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.45.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.47.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.35.8.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 213.35.11.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 213.35.40.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS9193 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 27 are in fix.csv.
- ROA: none19
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 144.34.58.0/23 | No ROA covers it. Add a ROA for AS9193, maxLength 23. |
| Route object: RIR | 144.34.58.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 62.32.96.0/23 | No ROA covers it. Add a ROA for AS9193, maxLength 23. |
| ROA: none | 62.32.105.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 62.32.106.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 62.32.108.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 62.32.110.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 62.32.111.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 207.45.112.0/20 | No ROA covers it. Add a ROA for AS9193, maxLength 20. |
| ROA: none | 213.35.4.0/22 | No ROA covers it. Add a ROA for AS9193, maxLength 22. |
| ROA: none | 213.35.10.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.33.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.34.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.37.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.43.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.45.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.47.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.8.0/23 | No ROA covers it. Add a ROA for AS9193, maxLength 23. |
| ROA: none | 213.35.11.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
| ROA: none | 213.35.40.0/24 | No ROA covers it. Add a ROA for AS9193, maxLength 24. |
Route objects not announced
Route objects with origin AS9193 whose prefix no peer sees AS9193 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.32.96.0/20 | RIPE | No ROA |
| 62.32.112.0/20 | RIPE | No ROA |
| 170.224.240.0/20 | RIPE-NONAUTH | No ROA |
| 192.86.45.0/24 | RIPE-NONAUTH | No ROA |
| 192.86.52.0/22 | RIPE-NONAUTH | No ROA |
| 213.35.0.0/18 | RIPE | No ROA |
| 2a02:74e0:20::/43 | 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.