Network · data from 2026-11-12
AS33934 VolgogradEC-AS PJSC Rostelecom
Registry name: VolgogradEC-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33934, 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.
| 83.239.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.128.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.132.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.138.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.142.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.151.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.152.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.156.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.158.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.162.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.164.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.167.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.168.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.172.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.184.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.188.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.191.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.120.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.126.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.168.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.80.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.84.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.208.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.63.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.70.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.80.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.84.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.100.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.20.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.23.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.24.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.30.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.44.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.47.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.48.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.66.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.70.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.74.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.76.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.78.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.85.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.87.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.107.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.126.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 178.34.64.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 178.35.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.0.0/17 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS33934 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS33934 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.