Network · data from 2026-11-12
AS14134 NAVISITE-WEST-2 - Navisite Opco LLC
Registry name: NAVISITE-WEST-2 - Navisite Opco LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14134, 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.
| 168.75.216.0/21 | No ROA | None | 673 100% |
AS-SET
AS14134 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 15 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.75.216.0/21 | No ROA covers it. Add a ROA for AS14134, maxLength 21. |
| Route object: none | 168.75.216.0/21 | No route object for it. Add a route object with origin AS14134 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14134 whose prefix no peer sees AS14134 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.231.210.0/23 | RADB | No ROA |
| 207.211.64.0/19 | RADB | No ROA |
| 207.211.64.0/20 | RADB | No ROA |
| 208.1.67.0/24 | RADB | No ROA |
| 208.1.68.0/24 | RADB | No ROA |
| 208.1.69.0/24 | RADB | No ROA |
| 208.1.70.0/24 | RADB | No ROA |
| 208.1.71.0/24 | RADB | No ROA |
| 208.222.96.0/23 | RADB | No ROA |
| 208.222.98.0/24 | RADB | No ROA |
| 216.10.96.0/19 | RADB | No ROA |
| 216.10.112.0/20 | RADB | No ROA |
| 216.243.64.0/20 | 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.