Network · data from 2026-11-12
AS8711 AVANTEL-BARNAUL-AS JSC "ER-Telecom Holding"
Registry name: AVANTEL-BARNAUL-AS JSC "ER-Telecom Holding", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8711, 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.
| 46.229.64.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.229.72.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 93.91.172.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 95.181.128.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 109.202.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 212.17.24.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 80.66.67.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS8711 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: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.229.64.0/22 | No ROA covers it. Add a ROA for AS8711, maxLength 22. |
| ROA: none | 46.229.72.0/23 | No ROA covers it. Add a ROA for AS8711, maxLength 23. |
| ROA: none | 93.91.172.0/23 | No ROA covers it. Add a ROA for AS8711, maxLength 23. |
| ROA: none | 95.181.128.0/22 | No ROA covers it. Add a ROA for AS8711, maxLength 22. |
| ROA: none | 109.202.8.0/22 | No ROA covers it. Add a ROA for AS8711, maxLength 22. |
| ROA: none | 212.17.24.0/23 | No ROA covers it. Add a ROA for AS8711, maxLength 23. |
Route objects not announced
Route objects with origin AS8711 whose prefix no peer sees AS8711 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.69.176.0/20 | RIPE | No ROA |
| 212.17.0.0/19 | RIPE | No ROA |
| 212.17.0.0/24 | RIPE | No ROA |
| 212.17.3.0/24 | RIPE | 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.