Network · data from 2026-11-12
AS30943 BIGWEB-AS ZAO Web Hosting
Registry name: BIGWEB-AS ZAO Web Hosting, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30943, 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.35.0/24 | Valid | Nonecovered by 217.112.34.0/23 | 672 100% |
| 217.112.32.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 217.112.34.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 217.112.40.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 217.112.47.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.112.44.0/24 | Valid | RIR databaseRIPE | 49 7%low visibility |
AS-SET
AS30943 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.
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.112.35.0/24 | No route object for it. A route object for 217.112.34.0/23 with origin AS30943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30943 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30943 whose prefix no peer sees AS30943 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.67.164.0/24 | RIPE | Invalid: origin |
| 185.67.165.0/24 | RIPE | Invalid: origin |
| 185.67.166.0/24 | RIPE | Invalid: origin |
| 185.67.167.0/24 | RIPE | Valid |
| 217.112.32.0/20 | RIPE | Valid |
| 217.112.36.0/22 | RIPE | Invalid: maxLength |
| 217.112.38.0/23 | RIPE | Invalid: maxLength |
| 217.112.40.0/22 | RIPE | Invalid: maxLength |
| 217.112.44.0/23 | RIPE | Invalid: maxLength |
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.