Network · data from 2026-11-12
AS53830 VPDC-1 - Otava, LLC
Registry name: VPDC-1 - Otava, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53830, 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.
| 74.123.86.0/23 | Valid | Nonecovered by 74.123.84.0/22 | 673 100% |
| 97.64.1.0/24 | Valid | Nonecovered by 97.64.0.0/23 | 673 100% |
| 199.119.104.0/22 | Valid | Nonecovered by 199.119.104.0/21 | 673 100% |
| 199.119.108.0/23 | Valid | Nonecovered by 199.119.104.0/21 | 673 100% |
| 199.119.110.0/23 | Valid | Nonecovered by 199.119.104.0/21 | 673 100% |
| 199.188.155.0/24 | Valid | Nonecovered by 199.188.152.0/22 | 673 100% |
| 204.13.180.0/23 | Valid | Nonecovered by 204.13.180.0/22 | 673 100% |
| 204.13.182.0/23 | Valid | Nonecovered by 204.13.180.0/22 | 673 100% |
| 74.123.85.0/24 | Valid | Nonecovered by 74.123.84.0/22 | 672 100% |
| 162.251.88.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.81.64.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.135.200.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.199.178.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.234.255.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 199.66.132.0/22 | Valid | RIR databaseARIN, NTTCOM | 673 100% |
| 204.13.180.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.68.132.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.71.190.0/23 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS53830 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 14 are in fix.csv.
- Route object: none9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 74.123.86.0/23 | No route object for it. A route object for 74.123.84.0/22 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 97.64.1.0/24 | No route object for it. A route object for 97.64.0.0/23 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 199.119.104.0/22 | No route object for it. A route object for 199.119.104.0/21 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 199.119.108.0/23 | No route object for it. A route object for 199.119.104.0/21 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 199.119.110.0/23 | No route object for it. A route object for 199.119.104.0/21 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 199.188.155.0/24 | No route object for it. A route object for 199.188.152.0/22 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 204.13.180.0/23 | No route object for it. A route object for 204.13.180.0/22 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 204.13.182.0/23 | No route object for it. A route object for 204.13.180.0/22 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
| Route object: none | 74.123.85.0/24 | No route object for it. A route object for 74.123.84.0/22 with origin AS53830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53830 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53830 whose prefix no peer sees AS53830 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.123.84.0/22 | ARIN, RADB | Valid |
| 97.64.0.0/23 | ARIN | Valid |
| 199.66.80.0/22 | RADB | No ROA |
| 199.119.104.0/21 | ARIN, RADB | Valid |
| 199.188.152.0/22 | ARIN, RADB | Valid |
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.