Network · data from 2026-11-12
AS40819 VPSDATACENTER - Liquid Web, L.L.C
Registry name: VPSDATACENTER - Liquid Web, L.L.C, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40819, 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.
| 67.20.54.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 67.20.55.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 104.207.236.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 104.207.238.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 104.207.240.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 104.207.253.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 173.249.146.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 173.249.148.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.240.189.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 209.126.28.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 173.249.144.0/24 | No ROA | Other IRR onlyALTDB, RADB | 672 100% |
| 173.249.147.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 2607:f7c0:4000::/40 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS40819 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 42 are in fix.csv.
- ROA: none13
- Route object: RIR13
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 67.20.54.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 67.20.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 67.20.55.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 67.20.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.207.236.0/23 | No ROA covers it. Add a ROA for AS40819, maxLength 23. |
| Route object: RIR | 104.207.236.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.207.238.0/23 | No ROA covers it. Add a ROA for AS40819, maxLength 23. |
| Route object: RIR | 104.207.238.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.207.240.0/22 | No ROA covers it. Add a ROA for AS40819, maxLength 22. |
| Route object: RIR | 104.207.240.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.207.253.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 104.207.253.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 173.249.146.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 173.249.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 173.249.148.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 173.249.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.240.189.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 192.240.189.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.126.28.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 209.126.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 173.249.144.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 173.249.144.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 173.249.147.0/24 | No ROA covers it. Add a ROA for AS40819, maxLength 24. |
| Route object: RIR | 173.249.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:f7c0:4000::/40 | No ROA covers it. Add a ROA for AS40819, maxLength 40. |
| Route object: RIR | 2607:f7c0:4000::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40819 whose prefix no peer sees AS40819 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.25.20.0/23 | RADB | No ROA |
| 69.25.20.0/24 | RADB | No ROA |
| 69.25.21.0/24 | RADB | No ROA |
| 72.44.85.0/24 | RADB | No ROA |
| 104.207.236.0/22 | RADB | No ROA |
| 104.207.236.0/24 | RADB | No ROA |
| 104.207.237.0/24 | RADB | No ROA |
| 104.207.238.0/24 | RADB | No ROA |
| 104.207.239.0/24 | RADB | No ROA |
| 104.207.240.0/24 | RADB | No ROA |
| 104.207.241.0/24 | RADB | No ROA |
| 104.207.242.0/24 | RADB | No ROA |
| 104.207.243.0/24 | RADB | No ROA |
| 173.249.144.0/20 | ALTDB | No ROA |
| 173.249.144.0/23 | ALTDB | No ROA |
| 173.249.156.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.