Network · data from 2026-11-12
AS197769 VPSDEDICATED-AS VPS Dedicated LLC
Registry name: VPSDEDICATED-AS VPS Dedicated LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197769, 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.
| 91.231.222.0/24 | Invalid: origin | None | 2 0%low visibility |
| 102.220.161.82/32 | Invalid: maxLength | None | 1 0%low visibility |
| 102.220.162.0/23 | Valid | None | 666 99% |
| 31.57.216.0/24 | Valid | None | 665 99% |
| 31.57.184.0/24 | Valid | None | 664 99% |
| 102.220.160.0/23 | Valid | None | 663 99% |
| 102.220.160.0/22 | Valid | Other origin only | 2 0%low visibility |
| 102.220.163.0/24 | Valid | None | 2 0%low visibility |
| 31.57.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 130.12.181.0/24 | Valid | RIR databaseARIN | 666 99% |
| 130.12.182.0/24 | Valid | RIR databaseARIN | 663 99% |
AS-SET
AS197769 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 10 are in fix.csv.
- ROA: origin1
- ROA: maxLength1
- Route object: none8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 91.231.222.0/24 | ROAs covering it name AS59623, not AS197769. If AS197769 should announce it, add a ROA for AS197769. |
| Route object: none | 91.231.222.0/24 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| ROA: maxLength | 102.220.161.82/32 | ROA 102.220.160.0/22 AS197769 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 102.220.161.82/32. |
| Route object: none | 102.220.161.82/32 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 102.220.162.0/23 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 31.57.216.0/24 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 31.57.184.0/24 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 102.220.160.0/23 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 102.220.160.0/22 | Route objects for it name AS51396. Add a route object with origin AS197769 in the RIR database for the space. |
| Route object: none | 102.220.163.0/24 | No route object for it. Add a route object with origin AS197769 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS197769 is announced.
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.