Network · data from 2026-11-12
AS21479 ROSTOV-TELEGRAF-AS PJSC Rostelecom
Registry name: ROSTOV-TELEGRAF-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21479, 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.
| 87.117.0.0/19 | Valid | Nonecovered by 87.117.0.0/18 | 672 100% |
| 80.68.0.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 80.68.8.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 80.254.96.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 83.221.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.36.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.40.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 93.178.96.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 93.178.104.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 93.178.126.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.64.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.65.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.68.12.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.68.13.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS21479 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 21 are in fix.csv.
- Route object: none1
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 87.117.0.0/19 | No route object for it. A route object for 87.117.0.0/18 with origin AS21479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21479 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21479 whose prefix no peer sees AS21479 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.41.64.0/19 | RIPE | Invalid: origin |
| 46.41.96.0/19 | RIPE | Invalid: origin |
| 80.254.96.0/20 | RIPE | Invalid: maxLength |
| 80.254.96.0/23 | RIPE | Invalid: maxLength |
| 83.221.192.0/20 | RIPE | Invalid: maxLength |
| 83.221.192.0/22 | RIPE | Invalid: maxLength |
| 83.221.204.0/22 | RIPE | Invalid: maxLength |
| 83.221.208.0/20 | RIPE | Invalid: maxLength |
| 83.221.208.0/21 | RIPE | Invalid: maxLength |
| 87.117.0.0/18 | RIPE | Valid |
| 87.117.8.0/21 | RIPE | Invalid: maxLength |
| 87.117.9.0/24 | RIPE | Invalid: maxLength |
| 87.117.12.0/22 | RIPE | Invalid: maxLength |
| 87.117.35.0/24 | RIPE | Invalid: maxLength |
| 93.178.96.0/19 | RIPE | Invalid: origin |
| 93.178.124.0/22 | RIPE | Invalid: origin |
| 109.165.0.0/17 | RIPE | Valid |
| 109.165.64.0/18 | RIPE | Invalid: maxLength |
| 188.114.0.0/19 | RIPE | Invalid: origin |
| 188.114.32.0/19 | RIPE | Invalid: origin |
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.