Network · data from 2026-11-12
AS8570 LES PJSC Rostelecom
Registry name: LES PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8570, 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.
| 95.179.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 95.179.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 95.179.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 95.179.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 95.179.80.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.179.96.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.32.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.40.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.64.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 178.234.192.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.224.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.224.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.232.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.240.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.34.248.0/21 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS8570 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 AS8570 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.