Network · data from 2026-11-12
AS199152 VDC-USA Virtual Data Center Inc
Registry name: VDC-USA Virtual Data Center Inc, US · not in PeeringDB
6IPv4 routes
83.3% RPKI valid · 100.0% with a route object
28IPv6 routes
100.0% RPKI valid · 28.6% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
20 with no route object for this origin
20Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS199152, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS199152, 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.
| 194.8.6.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a0a:2e86::/32 | Valid | None | 605 95% |
| 2a12:6705::/32 | Valid | None | 2 0%low visibility |
| 2a12:6706::/32 | Valid | None | 2 0%low visibility |
| 2a0a:2e83::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:1000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:2000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:3000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:4000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:5000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:6000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:7000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:8000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:9000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:a000::/36 | Valid | None | 1 0%low visibility |
| 2a0a:2e86:b000::/36 | Valid | None | 1 0%low visibility |
| 2a11:7e43::/36 | Valid | Nonecovered by 2a11:7e43::/32 | 1 0%low visibility |
| 2a11:8483::/36 | Valid | None | 1 0%low visibility |
| 2a11:8484::/32 | Valid | None | 1 0%low visibility |
| 2a11:df43::/36 | Valid | None | 1 0%low visibility |
| 2a12:6700::/32 | Valid | None | 1 0%low visibility |
| 91.239.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.19.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.242.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.22.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.21.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a11:7e41::/32 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:7e41:1::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:7e41:2::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:7e41:3::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:7e43::/32 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:7e47:b001::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:8480::/32 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:df47::/32 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS199152 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 31 are in fix.csv.
- ROA: none1
- Route object: none20
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.8.6.0/24 | No ROA covers it. Add a ROA for AS199152, maxLength 24. |
| Route object: none | 2a0a:2e86::/32 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a12:6705::/32 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a12:6706::/32 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e83::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:1000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:2000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:3000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:4000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:5000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:6000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:7000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:8000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:9000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:a000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a0a:2e86:b000::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a11:7e43::/36 | No route object for it. A route object for 2a11:7e43::/32 with origin AS199152 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a11:8483::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a11:8484::/32 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a11:df43::/36 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
| Route object: none | 2a12:6700::/32 | No route object for it. Add a route object with origin AS199152 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199152 whose prefix no peer sees AS199152 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.222.227.0/24 | RIPE | Invalid: origin |
| 94.247.137.0/24 | RIPE | Invalid: origin |
| 185.235.230.0/24 | RIPE | Invalid: origin |
| 212.22.77.0/24 | RIPE | Valid |
| 213.21.227.0/24 | RIPE | No ROA |
| 2a06:c3c0:1::/48 | RIPE | Valid |
| 2a06:e8c1::/32 | RIPE | Valid |
| 2a0a:2e81::/32 | RIPE | Valid |
| 2a0a:2e87::/32 | RIPE | Valid |
| 2a11:7e41::/48 | RIPE | 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.