Network · data from 2026-11-12
AS43991 VORONEZHTELECOM-AS Voronezh Telecom LLC
Registry name: VORONEZHTELECOM-AS Voronezh Telecom LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43991, 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.
| 185.144.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.144.60.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.144.62.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.144.62.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.61.232.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.8.88.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.132.131.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 84.252.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.215.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.249.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 170.168.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 170.168.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.42.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 189.74.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.19.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.135.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.187.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.228.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.26.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.243.83.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS43991 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: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.144.60.0/22 | No ROA covers it. Add a ROA for AS43991, maxLength 22. |
| ROA: none | 185.144.60.0/23 | No ROA covers it. Add a ROA for AS43991, maxLength 23. |
| ROA: none | 185.144.62.0/23 | No ROA covers it. Add a ROA for AS43991, maxLength 23. |
| ROA: none | 185.144.62.0/24 | No ROA covers it. Add a ROA for AS43991, maxLength 24. |
| ROA: none | 194.61.232.0/24 | No ROA covers it. Add a ROA for AS43991, maxLength 24. |
| ROA: none | 45.8.88.0/24 | No ROA covers it. Add a ROA for AS43991, maxLength 24. |
| ROA: none | 45.132.131.0/24 | No ROA covers it. Add a ROA for AS43991, maxLength 24. |
Route objects not announced
Route objects with origin AS43991 whose prefix no peer sees AS43991 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.144.60.0/24 | RIPE | No ROA |
| 185.144.61.0/24 | RIPE | No ROA |
| 185.144.63.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.