Network · data from 2026-11-12
AS24810 TELESET-KAZAN PJSC Rostelecom
Registry name: TELESET-KAZAN PJSC Rostelecom, RU · not in PeeringDB
54IPv4 routes
100.0% RPKI valid · 90.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
5 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS24810, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24810, 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.
| 81.22.202.0/24 | Valid | Nonecovered by 81.22.202.0/23 | 672 100% |
| 81.22.203.0/24 | Valid | Nonecovered by 81.22.202.0/23 | 672 100% |
| 81.23.148.0/24 | Valid | Other origin only | 672 100% |
| 81.23.149.0/24 | Valid | Other origin only | 672 100% |
| 81.23.158.0/24 | Valid | Other origin only | 672 100% |
| 81.22.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.205.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.206.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.207.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.208.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.209.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.210.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.211.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.212.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.213.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.214.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.22.215.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.23.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.23.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.23.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.23.156.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.23.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.164.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.166.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.167.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.168.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.190.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.112.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.124.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.248.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.128.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.129.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.130.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.132.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.20.135.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS24810 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 14 are in fix.csv.
- Route object: none5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 81.22.202.0/24 | No route object for it. A route object for 81.22.202.0/23 with origin AS24810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24810 in the RIR database for the space. |
| Route object: none | 81.22.203.0/24 | No route object for it. A route object for 81.22.202.0/23 with origin AS24810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24810 in the RIR database for the space. |
| Route object: none | 81.23.148.0/24 | Route objects for it name AS12389. Add a route object with origin AS24810 in the RIR database for the space. |
| Route object: none | 81.23.149.0/24 | Route objects for it name AS12389. Add a route object with origin AS24810 in the RIR database for the space. |
| Route object: none | 81.23.158.0/24 | Route objects for it name AS31185. Add a route object with origin AS24810 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24810 whose prefix no peer sees AS24810 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.22.200.0/21 | RIPE | Valid |
| 81.22.202.0/23 | RIPE | Invalid: maxLength |
| 81.22.204.0/22 | RIPE | Invalid: maxLength |
| 81.22.208.0/21 | RIPE | No ROA |
| 81.22.208.0/22 | RIPE | No ROA |
| 81.22.212.0/22 | RIPE | No ROA |
| 81.23.157.0/24 | RIPE | Invalid: origin |
| 178.20.128.0/21 | RIPE | Valid |
| 2a00:4f80::/32 | 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.