Network · data from 2026-11-12
AS20148 VANTIVA-CH - Vantiva USA Shared Services Inc.
Registry name: VANTIVA-CH - Vantiva USA Shared Services Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20148, 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.
| 141.11.8.0/24 | No ROA | Other origin only | 673 100% |
| 141.11.254.0/24 | No ROA | None | 673 100% |
| 205.143.193.0/24 | No ROA | None | 673 100% |
| 205.143.195.0/24 | No ROA | None | 673 100% |
| 205.143.198.0/24 | No ROA | None | 673 100% |
| 205.159.1.0/24 | Valid | RIR databaseARIN | 673 100% |
| 205.143.196.0/24 | Valid | RIR databaseARIN | 671 100% |
| 205.143.197.0/24 | Valid | RIR databaseARIN | 671 100% |
| 205.143.192.0/24 | Valid | RIR databaseARIN | 668 99% |
| 2001:5c8:f7fc::/48 | Valid | RIR databaseARIN | 634 100% |
| 2001:5c8:f7f9::/48 | Valid | RIR databaseARIN | 552 87% |
AS-SET
AS20148 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 16 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 141.11.8.0/24 | No ROA covers it. Add a ROA for AS20148, maxLength 24. |
| Route object: none | 141.11.8.0/24 | Route objects for it name AS205817. Add a route object with origin AS20148 in the RIR database for the space. |
| ROA: none | 141.11.254.0/24 | No ROA covers it. Add a ROA for AS20148, maxLength 24. |
| Route object: none | 141.11.254.0/24 | No route object for it. Add a route object with origin AS20148 in the RIR database for the space. |
| ROA: none | 205.143.193.0/24 | No ROA covers it. Add a ROA for AS20148, maxLength 24. |
| Route object: none | 205.143.193.0/24 | No route object for it. Add a route object with origin AS20148 in the RIR database for the space. |
| ROA: none | 205.143.195.0/24 | No ROA covers it. Add a ROA for AS20148, maxLength 24. |
| Route object: none | 205.143.195.0/24 | No route object for it. Add a route object with origin AS20148 in the RIR database for the space. |
| ROA: none | 205.143.198.0/24 | No ROA covers it. Add a ROA for AS20148, maxLength 24. |
| Route object: none | 205.143.198.0/24 | No route object for it. Add a route object with origin AS20148 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20148 whose prefix no peer sees AS20148 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.143.194.0/24 | ARIN | Valid |
| 208.83.88.0/22 | RIPE-NONAUTH | No ROA |
| 208.83.90.0/23 | RIPE-NONAUTH | No ROA |
| 208.83.90.0/24 | RIPE-NONAUTH | No ROA |
| 2001:5c8:f7fe::/48 | ARIN | Valid |
| 2001:5c8:f7ff::/48 | ARIN | 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.