Routing security
AS13118 ASN-YARTELECOM PJSC Rostelecom. Yaroslavl branch
Unclassified RIPE
RPKI valid
100%
41 of 41 announcements
RPKI invalid
0
none
No ROA
0
not covered by any ROA
IRR registered
100%
0 missing · 0 other origin
ROAs
37
authorising this AS
Announcements
What this network originates
Every prefix observed with AS13118 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 46.237.0.0/18 | RPKI valid | IRR | 54 |
| 46.237.0.0/19 | RPKI valid | IRR | 54 |
| 46.237.48.0/20 | RPKI valid | IRR | 54 |
| 77.234.0.0/19 | RPKI valid | IRR | 54 |
| 85.113.192.0/20 | RPKI valid | IRR | 54 |
| 85.113.204.0/24 | RPKI valid | IRR | 54 |
| 87.253.0.0/19 | RPKI valid | IRR | 54 |
| 87.253.0.0/20 | RPKI valid | IRR | 54 |
| 87.253.13.0/24 | RPKI valid | IRR | 54 |
| 87.253.16.0/21 | RPKI valid | IRR | 54 |
| 87.253.24.0/21 | RPKI valid | IRR | 54 |
| 93.181.208.0/20 | RPKI valid | IRR | 54 |
| 93.181.224.0/24 | RPKI valid | IRR | 54 |
| 93.181.225.0/24 | RPKI valid | IRR | 54 |
| 93.181.240.0/20 | RPKI valid | IRR | 54 |
| 95.86.192.0/19 | RPKI valid | IRR | 54 |
| 95.86.206.0/24 | RPKI valid | IRR | 54 |
| 95.86.207.0/24 | RPKI valid | IRR | 54 |
| 95.86.208.0/24 | RPKI valid | IRR | 54 |
| 95.86.209.0/24 | RPKI valid | IRR | 54 |
| 95.86.224.0/19 | RPKI valid | IRR | 54 |
| 95.106.160.0/19 | RPKI valid | IRR | 54 |
| 109.161.0.0/17 | RPKI valid | IRR | 54 |
| 109.161.0.0/19 | RPKI valid | IRR | 54 |
| 109.161.32.0/19 | RPKI valid | IRR | 54 |
| 109.161.57.0/24 | RPKI valid | IRR | 54 |
| 109.161.60.0/22 | RPKI valid | IRR | 54 |
| 109.161.64.0/19 | RPKI valid | IRR | 54 |
| 109.161.64.0/20 | RPKI valid | IRR | 54 |
| 217.15.128.0/19 | RPKI valid | IRR | 54 |
| 217.15.128.0/20 | RPKI valid | IRR | 54 |
| 217.15.134.0/24 | RPKI valid | IRR | 54 |
| 217.15.139.0/24 | RPKI valid | IRR | 54 |
| 217.15.141.0/24 | RPKI valid | IRR | 54 |
| 217.15.144.0/20 | RPKI valid | IRR | 54 |
| 217.15.145.0/24 | RPKI valid | IRR | 54 |
| 217.15.146.0/24 | RPKI valid | IRR | 54 |
| 217.15.147.0/24 | RPKI valid | IRR | 54 |
| 217.15.150.0/24 | RPKI valid | IRR | 54 |
| 217.15.151.0/24 | RPKI valid | IRR | 54 |
| 217.15.158.0/24 | RPKI valid | IRR | 54 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS13118 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 46.237.0.0/18 | /18 | RIPENCC |
| 46.237.0.0/19 | /19 | RIPENCC |
| 46.237.48.0/20 | /20 | RIPENCC |
| 77.234.0.0/19 | /19 | RIPENCC |
| 85.113.192.0/19 | /19 | RIPENCC |
| 85.113.192.0/20 | /20 | RIPENCC |
| 85.113.204.0/24 | /24 | RIPENCC |
| 87.253.0.0/19 | /19 | RIPENCC |
| 87.253.0.0/20 | /20 | RIPENCC |
| 87.253.13.0/24 | /24 | RIPENCC |
| 87.253.16.0/21 | /21 | RIPENCC |
| 87.253.24.0/21 | /21 | RIPENCC |
| 93.181.208.0/20 | /20 | RIPENCC |
| 93.181.224.0/24 | /24 | RIPENCC |
| 93.181.225.0/24 | /24 | RIPENCC |
| 93.181.240.0/20 | /20 | RIPENCC |
| 95.86.192.0/18 | /18 | RIPENCC |
| 95.86.192.0/19 | /19 | RIPENCC |
| 95.86.206.0/24 | /24 | RIPENCC |
| 95.86.207.0/24 | /24 | RIPENCC |
| 95.86.208.0/24 | /24 | RIPENCC |
| 95.86.209.0/24 | /24 | RIPENCC |
| 95.86.224.0/19 | /19 | RIPENCC |
| 95.106.160.0/19 | /19 | RIPENCC |
| 109.161.0.0/17 | /17 | RIPENCC |
| 109.161.0.0/19 | /19 | RIPENCC |
| 109.161.0.0/21 | /21 | RIPENCC |
| 109.161.8.0/21 | /21 | RIPENCC |
| 109.161.32.0/19 | /19 | RIPENCC |
| 109.161.52.0/24 | /24 | RIPENCC |
| 109.161.57.0/24 | /24 | RIPENCC |
| 109.161.60.0/22 | /22 | RIPENCC |
| 109.161.64.0/19 | /19 | RIPENCC |
| 109.161.64.0/20 | /20 | RIPENCC |
| 217.15.128.0/19 | /24 | RIPENCC |
| 217.15.134.0/24 | /24 | RIPENCC |
| 217.15.144.0/20 | /20 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS13118 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 46.237.32.0/20 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 46.237.40.0/21 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2019-10-11 | Not announced |
| 77.234.0.0/22 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2007-05-14 | Not announced |
| 77.234.4.0/22 | RIPE | Kostroma Unit of Telecommunication | YARTEL-MNT | 2010-11-18 | Not announced |
| 77.234.8.0/21 | RIPE | Kostroma Unit of Telecommunication | YARTEL-MNT | 2010-11-18 | Not announced |
| 77.234.16.0/21 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2007-07-13 | Not announced |
| 77.234.23.0/24 | RIPE | Kostroma Branch JSC Rostelecom | YARTEL-MNT | 2012-02-03 | Not announced |
| 77.234.24.0/21 | RIPE | Kostroma Unit of Telecommunication | YARTEL-MNT | 2010-11-18 | Not announced |
| 85.113.192.0/19 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 85.113.192.0/21 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-26 | Not announced |
| 85.113.192.0/24 | RIPE | Yaroslavl Unit of Telecommunication | YARTEL-MNT | 2005-11-25 | Not announced |
| 85.113.195.0/24 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2008-03-06 | Not announced |
| 85.113.208.0/22 | RIPE | Verhnevolzhsky branch | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.208.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.210.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.211.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.212.0/22 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 85.113.212.0/24 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.216.0/22 | RIPE | Verhnevolzhsky branch | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.216.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.217.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.218.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.219.0/24 | RIPE | Verhnevolzhsky branch | YARTEL-MNT | 2011-01-24 | Not announced |
| 85.113.220.0/22 | RIPE | Verhnevolzhsky branch | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.220.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.221.0/24 | RIPE | Verhnevolzhsky branch | YARTEL-MNT | 2011-01-24 | Not announced |
| 85.113.222.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 85.113.223.0/24 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 87.253.22.0/23 | RIPE | Joint Stock Company "Rostelecom" | YARTEL-MNT | 2018-11-19 | Not announced |
| 93.181.192.0/19 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 93.181.192.0/21 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2017-09-13 | Not announced |
| 93.181.200.0/21 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2017-09-13 | Not announced |
| 93.181.224.0/20 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-26 | Not announced |
| 93.181.248.0/22 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2012-12-06 | Not announced |
| 93.181.252.0/23 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2012-12-06 | Not announced |
| 93.181.254.0/23 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2012-11-21 | Not announced |
| 93.181.255.0/24 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2012-10-08 | Not announced |
| 95.86.192.0/18 | RIPE | Yartelecom | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 95.86.248.0/22 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2017-09-13 | Not announced |
| 95.86.248.0/24 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2016-03-01 | Not announced |
| 95.86.249.0/24 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2016-06-27 | Not announced |
| 95.86.252.0/22 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2017-09-13 | Not announced |
| 95.106.160.0/20 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 95.106.176.0/20 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 95.106.176.0/22 | RIPE | Joint Stock Company "Rostelecom" | YARTEL-MNT | 2017-09-13 | Not announced |
| 109.161.0.0/21 | RIPE | Technical Unit of Telecommunication | YARTEL-MNT | 2009-09-08 | Not announced |
| 109.161.8.0/21 | RIPE | Kostromskoy Branch | YARTEL-MNT | 2010-11-03 | Not announced |
| 109.161.50.0/23 | RIPE | Yaroslavl Branch | YARTEL-MNT | 2017-09-13 | Not announced |
| 109.161.52.0/22 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-26 | Not announced |
| 109.161.52.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 109.161.64.0/18 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-29 | Not announced |
| 109.161.104.0/21 | RIPE | Yaroslavsky Branch | YARTEL-MNT | 2018-10-26 | Not announced |
| 217.15.131.0/24 | RIPE | Yaroslavl Unit of Telecommunication | YARTEL-MNT | 2006-07-02 | Not announced |
| 217.15.132.0/24 | RIPE | Yartelecom | YARTEL-MNT | 2002-02-04 | Not announced |
| 217.15.133.0/24 | RIPE | Yartelecom | YARTEL-MNT | 2002-02-06 | Not announced |
| 217.15.135.0/24 | RIPE | Yartelecom | YARTEL-MNT | 2002-12-17 | Not announced |
| 217.15.144.0/24 | RIPE | Yartelecom | YARTEL-MNT | 2003-06-22 | Not announced |
| 217.15.149.0/24 | RIPE | Yaroslavl Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Not announced |
| 46.237.0.0/18 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 46.237.0.0/19 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 46.237.48.0/20 | RIPE | Kostromskoy Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 77.234.0.0/19 | RIPE | Kostromskoy Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 85.113.192.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 85.113.204.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 87.253.0.0/19 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 87.253.0.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 87.253.13.0/24 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 87.253.16.0/21 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 87.253.24.0/21 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 93.181.208.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 93.181.224.0/24 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 93.181.225.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 93.181.240.0/20 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.192.0/19 | RIPE | — | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.206.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.207.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.208.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.209.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.86.224.0/19 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 95.106.160.0/19 | RIPE | Joint Stock Company "Rostelecom" | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.0.0/17 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.0.0/19 | RIPE | Technical Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.32.0/19 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.57.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.60.0/22 | RIPE | Branch Yaroslavl-Kostroma | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.64.0/19 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 109.161.64.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.128.0/19 | RIPE | Yartelecom | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.128.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.134.0/24 | RIPE | Yartelecom | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.139.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.141.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.144.0/20 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.145.0/24 | RIPE | Yartelecom | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.146.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.147.0/24 | RIPE | Yaroslavl Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.150.0/24 | RIPE | Yaroslavl Unit of Telecommunication | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.151.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
| 217.15.158.0/24 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | 2024-12-23 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS13118 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS13118 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS13118 as a direct member |
AS-BTN-CUSTOMERS | RADB | Lists AS13118 as a direct member |
AS-HURRICANE | RADB | Lists AS13118 as a direct member |
AS-YARTELECOM | RIPE | Lists AS13118 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.