Network · data from 2026-11-12
AS25490 STC-AS PJSC Rostelecom
Registry name: STC-AS PJSC Rostelecom, RU · not in PeeringDB
87IPv4 routes
94.3% RPKI valid · 92.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
3RPKI invalid
0 origin · 3 maxLength
2No ROA
7 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS25490, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS25490, 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.
| 85.174.240.0/22 | Invalid: maxLength | Nonecovered by 85.174.240.0/20 | 67 10%low visibility |
| 85.174.248.0/22 | Invalid: maxLength | Nonecovered by 85.174.240.0/20 | 67 10%low visibility |
| 62.183.38.0/24 | Invalid: maxLength | Nonecovered by 62.183.32.0/20 | 66 10%low visibility |
| 91.230.54.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 193.33.132.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 83.239.207.0/24 | Valid | Nonecovered by 83.239.200.0/21 | 672 100% |
| 85.175.0.0/21 | Valid | Nonecovered by 85.175.0.0/19 | 672 100% |
| 85.175.2.0/24 | Valid | Nonecovered by 85.175.0.0/19 | 672 100% |
| 85.175.12.0/22 | Valid | Nonecovered by 85.175.0.0/19 | 672 100% |
| 62.183.32.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.48.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.52.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.56.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.60.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.64.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.64.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.88.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.92.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.183.96.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.0.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.40.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.200.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.224.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.240.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.244.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.64.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.79.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.82.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.84.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.96.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.104.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.108.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.160.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.144.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.150.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.152.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.156.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.128.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.132.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.136.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.143.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.190.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.224.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.252.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.14.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.46.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.62.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.65.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.66.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.72.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.82.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.96.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.100.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.152.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.170.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.194.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.216.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.226.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.175.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.144.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.233.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.172.72.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.174.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.174.227.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.174.230.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 85.174.232.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 85.174.250.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 62.183.0.0/19 | Valid | RIR databaseRIPE | 669 99% |
| 2a02:8040::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS25490 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 30 are in fix.csv.
- ROA: maxLength3
- ROA: none2
- Route object: none7
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 85.174.240.0/22 | ROA 85.174.240.0/20 AS25490 has maxLength 20; the route is a /22. Raise the maxLength, or add a ROA for 85.174.240.0/22. |
| Route object: none | 85.174.240.0/22 | No route object for it. A route object for 85.174.240.0/20 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| ROA: maxLength | 85.174.248.0/22 | ROA 85.174.240.0/20 AS25490 has maxLength 20; the route is a /22. Raise the maxLength, or add a ROA for 85.174.248.0/22. |
| Route object: none | 85.174.248.0/22 | No route object for it. A route object for 85.174.240.0/20 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| ROA: maxLength | 62.183.38.0/24 | ROA 62.183.32.0/20 AS25490 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 62.183.38.0/24. |
| Route object: none | 62.183.38.0/24 | No route object for it. A route object for 62.183.32.0/20 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| ROA: none | 91.230.54.0/24 | No ROA covers it. Add a ROA for AS25490, maxLength 24. |
| ROA: none | 193.33.132.0/23 | No ROA covers it. Add a ROA for AS25490, maxLength 23. |
| Route object: none | 83.239.207.0/24 | No route object for it. A route object for 83.239.200.0/21 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| Route object: none | 85.175.0.0/21 | No route object for it. A route object for 85.175.0.0/19 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| Route object: none | 85.175.2.0/24 | No route object for it. A route object for 85.175.0.0/19 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
| Route object: none | 85.175.12.0/22 | No route object for it. A route object for 85.175.0.0/19 with origin AS25490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25490 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25490 whose prefix no peer sees AS25490 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.183.0.0/23 | RIPE | Valid |
| 62.183.3.0/24 | RIPE | Valid |
| 62.183.4.0/22 | RIPE | Valid |
| 62.183.8.0/23 | RIPE | Valid |
| 62.183.10.0/24 | RIPE | Valid |
| 62.183.12.0/22 | RIPE | Valid |
| 62.183.16.0/22 | RIPE | Valid |
| 62.183.20.0/24 | RIPE | Valid |
| 62.183.23.0/24 | RIPE | Valid |
| 62.183.24.0/23 | RIPE | Valid |
| 62.183.28.0/23 | RIPE | Valid |
| 62.183.31.0/24 | RIPE | Valid |
| 85.173.4.0/22 | RIPE | Valid |
| 85.174.240.0/20 | RIPE | Valid |
| 85.174.240.0/23 | RIPE | Valid |
| 85.175.0.0/19 | RIPE | Valid |
| 85.175.200.0/21 | RIPE | Valid |
| 178.34.0.0/17 | RIPE | Valid |
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.