Network · data from 2026-11-12
AS18898 VESTA-CORP - Vesta Corporation
Registry name: VESTA-CORP - Vesta Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18898, 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.
| 66.193.40.0/25 | No ROA | None | 2 0%low visibility |
| 162.254.12.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 162.254.13.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 74.122.31.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 162.254.14.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 162.254.15.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 74.122.30.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS18898 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.193.40.0/25 | No ROA covers it. Add a ROA for AS18898, maxLength 25. |
| Route object: none | 66.193.40.0/25 | No route object for it. Add a route object with origin AS18898 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18898 whose prefix no peer sees AS18898 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.55.38.0/24 | RADB | No ROA |
| 66.97.132.0/24 | 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.