Network · data from 2026-11-12
AS40966 ValueHOST
Registry name: L7GUARD-AS ZAO Web Hosting, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40966, 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.
| 217.112.36.0/24 | Valid | Nonecovered by 217.112.36.0/23 | 673 100% |
| 217.112.32.0/20 | Valid | Other origin only | 80 12% |
| 185.67.164.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.112.36.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.112.42.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.112.45.0/24 | Valid | RIR databaseALTDB, RIPE | 673 100% |
| 217.112.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.112.44.0/24 | Valid | RIR databaseALTDB, RIPE | 623 93% |
| 185.67.164.0/24 | Valid | RIR databaseRIPE | 554 82% |
| 185.67.165.0/24 | Valid | RIR databaseRIPE | 554 82% |
| 185.67.166.0/24 | Valid | RIR databaseRIPE | 554 82% |
| 185.67.167.0/24 | Valid | RIR databaseRIPE | 554 82% |
AS-SET
AS40966's PeeringDB record names no 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 2 are in fix.csv.
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.112.36.0/24 | No route object for it. A route object for 217.112.36.0/23 with origin AS40966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40966 in the RIR database for the space. |
| Route object: none | 217.112.32.0/20 | Route objects for it name AS30943. Add a route object with origin AS40966 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS40966 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.