Network · data from 2026-11-12
AS13118 ASN-YARTELECOM PJSC Rostelecom
Registry name: ASN-YARTELECOM PJSC Rostelecom, RU · not in PeeringDB
41IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
58Route objects not announced
registered with origin AS13118, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13118, 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.
| 46.237.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 46.237.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 46.237.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 77.234.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 85.113.192.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 85.113.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.253.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 87.253.0.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 87.253.13.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.253.16.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 87.253.24.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 93.181.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 93.181.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 93.181.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 93.181.240.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.206.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.207.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.208.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.209.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.86.224.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 95.106.160.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.57.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.60.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.161.64.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.128.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.144.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.151.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.15.158.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS13118 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 58 are in fix.csv.
- Route object: not announced58
Route objects not announced
Route objects with origin AS13118 whose prefix no peer sees AS13118 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.237.32.0/20 | RIPE | Invalid: maxLength |
| 46.237.40.0/21 | RIPE | Invalid: maxLength |
| 77.234.0.0/22 | RIPE | Invalid: maxLength |
| 77.234.4.0/22 | RIPE | Invalid: maxLength |
| 77.234.8.0/21 | RIPE | Invalid: maxLength |
| 77.234.16.0/21 | RIPE | Invalid: maxLength |
| 77.234.23.0/24 | RIPE | Invalid: maxLength |
| 77.234.24.0/21 | RIPE | Invalid: maxLength |
| 85.113.192.0/19 | RIPE | Valid |
| 85.113.192.0/21 | RIPE | Invalid: maxLength |
| 85.113.192.0/24 | RIPE | Invalid: maxLength |
| 85.113.195.0/24 | RIPE | Invalid: maxLength |
| 85.113.208.0/22 | RIPE | Invalid: maxLength |
| 85.113.208.0/24 | RIPE | Invalid: maxLength |
| 85.113.210.0/24 | RIPE | Invalid: maxLength |
| 85.113.211.0/24 | RIPE | Invalid: maxLength |
| 85.113.212.0/22 | RIPE | Invalid: maxLength |
| 85.113.212.0/24 | RIPE | Invalid: maxLength |
| 85.113.216.0/22 | RIPE | Invalid: maxLength |
| 85.113.216.0/24 | RIPE | Invalid: maxLength |
| 85.113.217.0/24 | RIPE | Invalid: maxLength |
| 85.113.218.0/24 | RIPE | Invalid: maxLength |
| 85.113.219.0/24 | RIPE | Invalid: maxLength |
| 85.113.220.0/22 | RIPE | Invalid: maxLength |
| 85.113.220.0/24 | RIPE | Invalid: maxLength |
| 85.113.221.0/24 | RIPE | Invalid: maxLength |
| 85.113.222.0/24 | RIPE | Invalid: maxLength |
| 85.113.223.0/24 | RIPE | Invalid: maxLength |
| 87.253.22.0/23 | RIPE | Invalid: maxLength |
| 93.181.192.0/19 | RIPE | No ROA |
| 93.181.192.0/21 | RIPE | Invalid: origin |
| 93.181.200.0/21 | RIPE | Invalid: origin |
| 93.181.224.0/20 | RIPE | No ROA |
| 93.181.248.0/22 | RIPE | Invalid: maxLength |
| 93.181.252.0/23 | RIPE | Invalid: maxLength |
| 93.181.254.0/23 | RIPE | Invalid: maxLength |
| 93.181.255.0/24 | RIPE | Invalid: maxLength |
| 95.86.192.0/18 | RIPE | Valid |
| 95.86.248.0/22 | RIPE | Invalid: maxLength |
| 95.86.248.0/24 | RIPE | Invalid: maxLength |
| 95.86.249.0/24 | RIPE | Invalid: maxLength |
| 95.86.252.0/22 | RIPE | Invalid: maxLength |
| 95.106.160.0/20 | RIPE | Invalid: maxLength |
| 95.106.176.0/20 | RIPE | Invalid: maxLength |
| 95.106.176.0/22 | RIPE | Invalid: maxLength |
| 109.161.0.0/21 | RIPE | Valid |
| 109.161.8.0/21 | RIPE | Valid |
| 109.161.50.0/23 | RIPE | Invalid: maxLength |
| 109.161.52.0/22 | RIPE | Invalid: maxLength |
| 109.161.52.0/24 | RIPE | Valid |
| 109.161.64.0/18 | RIPE | Invalid: maxLength |
| 109.161.104.0/21 | RIPE | Invalid: maxLength |
| 217.15.131.0/24 | RIPE | Valid |
| 217.15.132.0/24 | RIPE | Valid |
| 217.15.133.0/24 | RIPE | Valid |
| 217.15.135.0/24 | RIPE | Valid |
| 217.15.144.0/24 | RIPE | Valid |
| 217.15.149.0/24 | 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.