Network · data from 2026-11-12
AS46407 AS-VULTR3 - The Constant Company, LLC
Registry name: AS-VULTR3 - The Constant Company, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46407, 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.
| 2001:19f0:5404::/48 | Valid | Nonecovered by 2001:19f0:5404::/46 | 635 100% |
| 173.199.108.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.167.225.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 173.199.98.0/24 | Valid | RIR databaseARIN | 672 100% |
| 45.63.45.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 2001:19f0:a08::/48 | Valid | RIR databaseARIN, RADB | 636 100% |
| 2a05:f480:10::/48 | Valid | RIR databaseRADB, RIPE | 636 100% |
AS-SET
AS46407 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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2001:19f0:5404::/48 | No route object for it. A route object for 2001:19f0:5404::/46 with origin AS46407 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46407 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46407 whose prefix no peer sees AS46407 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 173.199.99.0/24 | ARIN, RADB | Valid |
| 2001:19f0:ff::/48 | ARIN | Valid |
| 2001:19f0:a06::/48 | ARIN | Valid |
| 2001:19f0:a07::/48 | ARIN | Valid |
| 2001:19f0:5404::/46 | ARIN, RADB | Valid |
| 2602:ff03::/36 | 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.