Routing security
AS8359 MTS
Mobile RIPE Cable/DSL/ISP
Announcements
What this network originates
Every prefix observed with AS8359 as its origin, checked against RPKI and the IRR. Problems sort first.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS8359 may originate these prefixes, up to the maximum length shown.
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 AS8359 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 |
|---|---|---|---|---|---|
| 5.144.64.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 5.189.213.0/24 | RIPE | PJSC Mobile TeleSystems Stavropolskiy kray branch | MTU-NOC | 2025-06-17 | Not announced |
| 5.227.0.0/16 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 5.227.105.0/24 | RIPE | PJSC Mobile TeleSystems Tambov region branch | MTU-NOC | 2026-10-07 | Not announced |
| 31.29.128.0/17 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 37.72.64.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 45.151.228.0/22 | RIPE | MTS PJSC | MTU-NOC | 2019-09-13 | Not announced |
| 46.148.254.0/23 | RIPE | MTS_Kemerovo | MTU-NOC | 2025-03-04 | Not announced |
| 46.232.160.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 62.105.48.0/20 | RIPE | MTS PJSC, M2M | MTU-NOC | 2020-09-08 | Not announced |
| 62.113.87.0/24 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2019-10-11 | Not announced |
| 62.118.66.0/24 | RIPE | Mobile TeleSystems Smolensk branch | MTU-NOC | 2025-01-24 | Not announced |
| 62.118.72.0/22 | RIPE | MTS Volga | MTU-NOC | 2022-01-14 | Not announced |
| 62.118.80.0/22 | RIPE | MTS Volga | MTU-NOC | 2022-01-14 | Not announced |
| 62.220.32.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 77.66.176.0/20 | RIPE | MTS PJSC Krasnodar region | MTU-NOC | 2023-11-13 | Not announced |
| 77.66.184.0/21 | RIPE | — | MTU-NOC | 2021-03-10 | Not announced |
| 77.66.200.0/21 | RIPE | MTS PJSC Krasnodar region | MTU-NOC | 2023-11-13 | Not announced |
| 77.87.80.0/21 | RIPE | PJSC Mobile TeleSystems Omsk branch | MTU-NOC | 2026-09-30 | Not announced |
| 77.220.32.0/19 | RIPE | — | MTU-NOC | 2025-01-24 | Not announced |
| 77.220.60.0/22 | RIPE | MTS route object | MTU-NOC | 2021-01-20 | Not announced |
| 77.239.192.0/20 | RIPE | PJSC Mobile TeleSystems Surgut and KHMAO branch | MTU-NOC | 2023-05-29 | Not announced |
| 77.239.192.0/23 | RIPE | MTS Surgut and KHMAO branch (FBN) | MTU-NOC | 2023-05-29 | Not announced |
| 77.239.216.0/22 | RIPE | — | MTU-NOC | 2023-06-07 | Not announced |
| 77.239.220.0/22 | RIPE | — | MTU-NOC | 2023-06-07 | Not announced |
| 78.109.32.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 78.109.46.0/23 | RIPE | MTS DV | MTU-NOC | 2020-06-17 | Not announced |
| 79.143.236.0/24 | RIPE | PJSC Mobile TeleSystems Tambov region branch | MTU-NOC | 2026-03-31 | Not announced |
| 80.71.160.0/19 | RIPE | MTS Barnaul | MTU-NOC | 2026-08-24 | Not announced |
| 80.71.179.0/24 | RIPE | MTS Barnaul | MTU-NOC | 2026-08-28 | Not announced |
| 80.71.183.0/24 | RIPE | MTS Barnaul | MTU-NOC | 2026-08-28 | Not announced |
| 80.83.224.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 80.83.224.0/23 | RIPE | Mobile TeleSystems, PJSC, MR DV | MTU-NOC | 2020-06-17 | Not announced |
| 80.83.224.0/24 | RIPE | Mobile TeleSystems, PJSC, MR DV | MTU-NOC | 2020-06-17 | Not announced |
| 80.83.226.0/23 | RIPE | Mobile TeleSystems, OJSC | MTU-NOC | 2024-11-07 | Not announced |
| 80.83.232.0/22 | RIPE | Mobile TeleSystems, PJSC, MR DV | MTU-NOC | 2020-06-17 | Not announced |
| 80.83.236.0/22 | RIPE | Mobile TeleSystems, PJSC, MR DV | MTU-NOC | 2020-06-17 | Not announced |
| 80.255.176.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 80.255.180.0/24 | RIPE | MTS Magadan | MTU-NOC | 2020-12-22 | Not announced |
| 81.195.131.0/24 | RIPE | PJSC Mobile TeleSystems Belgorod region branch | MTU-NOC | 2026-02-02 | Not announced |
| 81.195.138.0/23 | RIPE | Mobile TeleSystems Tambov branch (b2b) | MTU-NOC | 2026-09-18 | Not announced |
| 81.195.144.0/24 | RIPE | PJSC Mobile TeleSystems Ivanovo region branch | MTU-NOC | 2026-01-21 | Not announced |
| 81.195.145.0/24 | RIPE | PJSC Mobile TeleSystems Irkutsk region branch | MTU-NOC | 2026-03-04 | Not announced |
| 81.195.151.0/24 | RIPE | PJSC Mobile TeleSystems Kursk region branch | MTU-NOC | 2026-01-22 | Not announced |
| 81.195.164.0/24 | RIPE | PJSC Mobile TeleSystems Tula region branch | MTU-NOC | 2026-01-28 | Not announced |
| 81.195.172.0/24 | RIPE | PJSC Mobile TeleSystems Ryazan' region branch | MTU-NOC | 2026-01-23 | Not announced |
| 81.195.178.0/24 | RIPE | PJSC Mobile TeleSystems Yaroslavl region branch | MTU-NOC | 2026-01-15 | Not announced |
| 84.17.251.0/24 | RIPE | MTS Orel broadband network (b2b) | MTU-NOC | 2022-05-19 | Not announced |
| 85.140.0.0/21 | RIPE | MTS gprs-infra in Volga-region | MTU-NOC | 2015-08-05 | Not announced |
| 85.140.76.0/22 | RIPE | MTS gprs-infra in Ural-region | MTU-NOC | 2015-10-30 | Not announced |
| 85.141.0.0/20 | RIPE | PJSC "MTS" Centr MBN | MTU-NOC | 2026-10-05 | Not announced |
| 85.141.40.0/21 | RIPE | PJSC "MTS" Centr MBN | MTU-NOC | 2026-10-05 | Not announced |
| 85.141.64.0/21 | RIPE | Moscow | MTU-NOC | 2023-08-15 | Not announced |
| 85.141.72.0/21 | RIPE | Moscow | MTU-NOC | 2023-08-15 | Not announced |
| 85.141.88.0/22 | RIPE | Krasnodar | MTU-NOC | 2023-08-15 | Not announced |
| 85.234.32.0/19 | RIPE | — | MTU-NOC | 2023-04-04 | Not announced |
| 89.22.188.0/22 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 89.148.192.0/18 | RIPE | DELEGATED BLOCK | MTU-NOC | 2025-12-08 | Not announced |
| 89.251.96.0/20 | RIPE | PJSC "MTS" Siberia | MTU-NOC | 2022-02-24 | Not announced |
| 91.76.0.0/14 | RIPE | ZAO MTU-Intel's Moscow Region Network | MTU-NOC | 2006-09-13 | Not announced |
| 91.90.32.0/21 | RIPE | PJSC Mobile TeleSystems Omsk branch | MTU-NOC | 2026-09-30 | Not announced |
| 91.185.64.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 91.190.64.0/20 | RIPE | Lipetsk Zelenaya Tochka PSI | MTU-NOC | 2026-07-09 | Not announced |
| 91.211.124.0/22 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 91.224.208.0/23 | RIPE | MultiCable Network Kislovodsk JSC | KUBANGSM-MNT | 2025-08-21 | Not announced |
| 92.246.192.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 93.187.176.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 94.125.240.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 94.138.152.0/21 | RIPE | PJSC MTS Customers | MTU-NOC | 2024-03-06 | Not announced |
| 94.199.72.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 94.229.224.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 94.243.0.0/18 | RIPE | Mobile TeleSystems | MTU-NOC | 2025-07-28 | Not announced |
| 94.243.52.0/22 | RIPE | PJSC Mobile TeleSystems Kaluga branch | MTU-NOC | 2025-11-18 | Not announced |
| 94.243.56.0/22 | RIPE | PJSC Mobile TeleSystems Kaluga branch | MTU-NOC | 2025-11-18 | Not announced |
| 95.104.192.0/18 | RIPE | MTS PJSC | MTU-NOC | 2022-09-08 | Not announced |
| 95.139.40.0/21 | RIPE | MTS PJSC Krasnodar region | MTU-NOC | 2023-11-13 | Not announced |
| 95.139.96.0/21 | RIPE | — | MTU-NOC | 2023-11-13 | Not announced |
| 95.215.12.0/22 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 109.198.64.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 109.198.72.0/21 | RIPE | MTS Surgut and KHMAO branch (FBN) | MTU-NOC | 2023-05-29 | Not announced |
| 176.65.96.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 176.118.16.0/22 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2019-07-17 | Not announced |
| 176.222.192.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 176.241.96.0/23 | RIPE | RU-LANCK-Lbk-Home-SPB | LANCK-MNT | 2012-08-21 | Not announced |
| 178.155.0.0/19 | RIPE | — | MTU-NOC | 2023-11-13 | Not announced |
| 178.155.56.0/22 | RIPE | MTS PJSC | MTU-NOC | 2025-11-25 | Not announced |
| 178.155.60.0/22 | RIPE | MTS PJSC | MTU-NOC | 2025-11-25 | Not announced |
| 178.218.96.0/20 | RIPE | Mobile TeleSystems Komsomolsk-na-Amure, fixed broadband access | MTU-NOC | 2023-06-14 | Not announced |
| 185.35.192.0/23 | RIPE | — | MTU-NOC | 2023-11-13 | Not announced |
| 185.59.138.0/24 | RIPE | MTS Russian Service Network | MTU-NOC | 2017-05-02 | Not announced |
| 185.59.139.0/24 | RIPE | MTS Russian Service Network | MTU-NOC | 2017-05-02 | Not announced |
| 185.190.164.0/22 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 185.190.164.0/24 | RIPE | MTS PJSC | MTU-NOC | 2021-01-29 | Not announced |
| 185.190.165.0/24 | RIPE | MTS PJSC | MTU-NOC | 2021-01-29 | Not announced |
| 185.242.16.0/24 | RIPE | MTS eSport | MTU-NOC | 2020-12-01 | Not announced |
| 188.75.192.0/20 | RIPE | MTS Zabaikalskiy krai | MTU-NOC | 2026-01-15 | Not announced |
| 188.75.216.0/23 | RIPE | PJSC Mobile TeleSystems Amur region branch | MTU-NOC | 2026-06-10 | Not announced |
| 188.75.218.0/23 | RIPE | PJSC Mobile TeleSystems Amur region branch | MTU-NOC | 2026-06-10 | Not announced |
| 188.75.220.0/22 | RIPE | MTS Zabaikalskiy krai | MTU-NOC | 2026-01-15 | Not announced |
| 188.75.252.0/22 | RIPE | MTS Zabaikalskiy krai | MTU-NOC | 2026-01-15 | Not announced |
| 188.191.80.0/20 | RIPE | Mobile TeleSystems Komsomolsk-na-Amure, fixed broadband access | MTU-NOC | 2023-06-14 | Not announced |
| 193.8.208.0/22 | RIPE | MTS PJSC | MTU-NOC | 2025-03-10 | Not announced |
| 193.22.149.0/24 | RIPE | MTS PJSC | MTU-NOC | 2023-08-07 | Not announced |
| 193.27.230.0/23 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 193.32.196.0/23 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 193.169.36.0/23 | RIPE | Mobile TeleSystems Komsomolsk-na-Amure, fixed broadband access | MTU-NOC | 2023-06-14 | Not announced |
| 195.34.0.0/18 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 195.222.128.0/19 | RIPE | PJSC "MTS" | MTU-NOC | 2025-02-21 | Not announced |
| 212.30.133.0/24 | RIPE | — | MTU-NOC | 2022-12-13 | Not announced |
| 212.77.128.0/20 | RIPE | Mobile TeleSystems Mezhdurechensk branch (former RIKT) | MTU-NOC | 2025-11-24 | Not announced |
| 212.109.200.0/21 | RIPE | MTS PJSC | MTU-NOC | 2021-11-08 | Not announced |
| 212.188.1.0/24 | RIPE | — | MTU-NOC | 2025-01-06 | Not announced |
| 212.188.15.0/24 | RIPE | Google net MTS MRDV | MTU-NOC | 2020-06-16 | Not announced |
| 212.188.16.0/24 | RIPE | — | MTU-NOC | 2025-01-06 | Not announced |
| 212.188.29.0/24 | RIPE | — | MTU-NOC | 2025-01-06 | Not announced |
| 213.27.32.0/19 | RIPE | Mobile TeleSystems, South branch | MTU-NOC | 2024-07-15 | Not announced |
| 213.59.132.0/22 | RIPE | — | MTU-NOC | 2026-07-09 | Not announced |
| 213.59.155.0/24 | RIPE | — | MTU-NOC | 2026-07-09 | Not announced |
| 213.59.158.0/24 | RIPE | — | MTU-NOC | 2026-07-09 | Not announced |
| 213.87.80.0/23 | RIPE | Mobile TeleSystems OJSC | MTU-NOC | 2025-08-18 | Not announced |
| 213.87.82.0/23 | RIPE | Mobile TeleSystems OJSC | MTU-NOC | 2025-08-18 | Not announced |
| 213.87.96.0/23 | RIPE | Vladivostok (Far East) division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-17 | Not announced |
| 213.87.96.0/24 | RIPE | Vladivostok (Far East) division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-17 | Not announced |
| 213.87.97.0/24 | RIPE | Vladivostok (Far East) division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-17 | Not announced |
| 213.87.100.0/22 | RIPE | MR DV division of Mobile Telesystems PJSC | MTU-NOC | 2025-11-28 | Not announced |
| 213.87.104.0/23 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-16 | Not announced |
| 213.87.108.0/23 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-16 | Not announced |
| 213.87.110.0/23 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | 2020-06-16 | Not announced |
| 213.87.128.0/20 | RIPE | Mobile TeleSystems, PJSC, NAT for GPRS/3G | MTSNET-MNT | 2015-08-05 | Not announced |
| 213.87.144.0/20 | RIPE | Mobile TeleSystems, PJSC, NAT for GPRS/3G | MTSNET-MNT | 2015-08-25 | Not announced |
| 213.87.200.0/21 | RIPE | Mobile TeleSystems, OJSC | MTU-NOC | 2013-10-03 | Not announced |
| 213.87.204.0/22 | RIPE | Mobile TeleSystems, PJSC | MTSNET-MNT | 2016-03-04 | Not announced |
| 213.176.224.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Not announced |
| 217.66.144.0/20 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.66.147.0/24 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.66.152.0/23 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.66.155.0/24 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.66.156.0/23 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.66.158.0/23 | RIPE | Mobile TeleSystems PJSC, North-West division | MR-NW-MTS-MNT | 2016-06-04 | Not announced |
| 217.74.240.0/20 | RIPE | KUBANGSM-NET | KUBANGSM-MNT | 2022-09-08 | Not announced |
| 217.107.196.0/22 | RIPE | Lipetsk Zelenaya Tochka | MTU-NOC | 2026-07-09 | Not announced |
| 2a00:1fa0::/29 | RIPE | MTS ipv6 for Mobile | MTU-NOC | 2017-06-29 | Not announced |
| 2a00:1fa0::/32 | RIPE | MTS Moscow/Center Mobile ipv6 | MTU-NOC | 2016-06-30 | Not announced |
| 2a00:1fa1::/32 | RIPE | MTS Ural Mobile ipv6 | MTU-NOC | 2016-06-30 | Not announced |
| 2a00:1fa7::/32 | RIPE | MTS ipv6 for Mobile | MTU-NOC | 2026-05-15 | Not announced |
| 2a00:1fa7:b000::/36 | RIPE | PJSC "MTS" Kamchatka MBN | MTU-NOC | 2026-06-05 | Not announced |
| 2a01:8043::/36 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2022-12-15 | Not announced |
| 2a02:28::/48 | RIPE | MTS ipv6 backbone | MTU-NOC | 2021-03-18 | Not announced |
| 2a02:3f8::/32 | RIPE | EMTS-V6 | MTU-NOC | 2021-01-11 | Not announced |
| 2a03:7201::/32 | RIPE | PJSC MTS Kursk | MTU-NOC | 2015-12-21 | Not announced |
| 2a03:7203::/36 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2023-03-17 | Not announced |
| 5.144.96.0/19 | RIPE | Mobile TeleSystems PJSC, Saint-Petersburg division | LANCK-MNT | 2016-06-04 | Announced |
| 5.144.125.0/24 | RIPE | Mobile TeleSystems, OJSC | MTU-NOC | 2024-11-07 | Announced |
| 5.189.208.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Announced |
| 5.189.214.0/24 | RIPE | PJSC Mobile TeleSystems Stavropolskiy kray branch (b2b) | MTU-NOC | 2025-06-09 | Announced |
| 5.227.96.0/20 | RIPE | Mobile TeleSystems Volga branch (b2b/b2c) | MTU-NOC | 2026-07-24 | Announced |
| 5.227.118.0/24 | RIPE | MTS ipv4 broadband network Nizhny Novgorod (b2b) | MTU-NOC | 2022-10-18 | Announced |
| 5.227.119.0/24 | RIPE | MTS Velikiy Novgorod | MTU-NOC | 2021-11-10 | Announced |
| 5.227.120.0/23 | RIPE | Mobile TeleSystems OJSC | MTU-NOC | 2025-08-14 | Announced |
| 5.227.160.0/23 | RIPE | Tomsk | MTU-NOC | 2024-12-09 | Announced |
| 5.227.162.0/24 | RIPE | Mobile TeleSystems Samara branch (b2b) | MTU-NOC | 2025-03-07 | Announced |
| 5.227.164.0/22 | RIPE | PJSC Mobile TeleSystems Altay region branch (b2b) | MTU-NOC | 2025-01-29 | Announced |
| 5.227.170.0/23 | RIPE | Mobile TeleSystems Volzhsk branch (b2b) | MTU-NOC | 2025-10-30 | Announced |
| 31.15.80.0/20 | RIPE | Progtech-Yug Ltd | MTU-NOC | 2023-07-25 | Announced |
| 31.29.146.0/24 | RIPE | Mobile TeleSystems, OJSC, Ufa | MTU-NOC | 2025-12-12 | Announced |
| 31.29.150.0/24 | RIPE | PJSC Mobile TeleSystems Samara branch (b2b) | MTU-NOC | 2025-12-15 | Announced |
| 31.29.151.0/24 | RIPE | Mobile TeleSystems, OJSC, Ufa | MTU-NOC | 2025-11-25 | Announced |
| 31.29.177.0/24 | RIPE | PJSC "MTS" Mordovia | MTU-NOC | 2025-10-02 | Announced |
| 31.40.112.0/20 | RIPE | MTS Miass | MTU-NOC | 2024-04-12 | Announced |
| 31.131.92.0/22 | RIPE | MTS eSport | MTU-NOC | 2020-12-01 | Announced |
| 37.139.192.0/18 | RIPE | Mobile TeleSystems Mezhdurechensk branch (former RIKT) | MTU-NOC | 2025-11-24 | Announced |
| 37.208.96.0/21 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Announced |
| 37.208.96.0/22 | RIPE | PJSC Mobile TeleSystems YANAO branch | MTU-NOC | 2025-12-10 | Announced |
| 37.208.120.0/21 | RIPE | COMSTAR_MGN_NET | MTU-NOC | 2024-03-29 | Announced |
| 46.20.176.0/20 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2026-09-23 | Announced |
| 46.20.185.0/24 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2023-09-21 | Announced |
| 46.20.186.0/24 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2023-09-21 | Announced |
| 46.20.187.0/24 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2022-06-24 | Announced |
| 46.20.188.0/24 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2022-05-19 | Announced |
| 46.20.190.0/24 | RIPE | MTS Vladimir broadband network (b2b) | MTU-NOC | 2023-10-10 | Announced |
| 46.23.184.0/21 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2025-08-14 | Announced |
| 46.148.240.0/20 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Announced |
| 46.148.240.0/22 | RIPE | MTS Blagoveschensk | MTU-NOC | 2021-11-01 | Announced |
| 46.148.240.0/24 | RIPE | MTS PJSC | MTU-NOC | 2022-09-08 | Announced |
| 46.148.244.0/24 | RIPE | MTS broadband network Tula (b2b) | MTU-NOC | 2022-10-20 | Announced |
| 46.148.245.0/24 | RIPE | MTS Krasnodar broadband network (b2b) | MTU-NOC | 2022-06-09 | Announced |
| 46.232.164.0/23 | RIPE | MTS Bashkortostan | MTU-NOC | 2017-10-30 | Announced |
| 46.250.64.0/19 | RIPE | PJSC MTS | MTU-NOC | 2022-03-31 | Announced |
| 46.250.76.0/23 | RIPE | PJSC Mobile TeleSystems YANAO branch | MTU-NOC | 2025-12-10 | Announced |
| 62.5.128.0/17 | RIPE | PTTNET's first /17 block | MTU-NOC | 2004-01-22 | Announced |
| 62.105.44.0/22 | RIPE | MTS PJSC, Groznyi | MTU-NOC | 2020-09-08 | Announced |
| 62.105.48.0/21 | RIPE | MTS PJSC, M2M, Moscow | MTU-NOC | 2020-06-26 | Announced |
| 62.105.56.0/23 | RIPE | MTS PJSC, M2M, Ural | MTU-NOC | 2020-06-26 | Announced |
| 62.105.58.0/23 | RIPE | MTS PJSC, M2M, North-West | MTU-NOC | 2020-11-26 | Announced |
| 62.105.60.0/23 | RIPE | MTS PJSC, M2M, Siberia | MTU-NOC | 2023-10-30 | Announced |
| 62.105.62.0/23 | RIPE | MTS PJSC, M2M, Far-East | MTU-NOC | 2021-08-18 | Announced |
| 62.113.88.0/24 | RIPE | Mobile TeleSystems PJSC | MTU-NOC | 2019-10-11 | Announced |
| 62.118.0.0/16 | RIPE | ZAO MTU-Intel's Moscow Region Network | MTU-NOC | 2003-08-22 | Announced |
| 62.118.84.0/22 | RIPE | MTS Siberia | MTU-NOC | 2021-04-06 | Announced |
| 62.118.128.0/19 | RIPE | Comstar-Regions's Velikiy Novgorod Region Network | MTU-NOC | 2011-11-17 | Announced |
Showing 200 of 581.
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS8359 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-MTU | PeeringDB | Declared by the operator as its own set |
AS-MTU-V6 | PeeringDB | Declared by the operator as its own set |
AS-10099 | RADB | Lists AS8359 as a direct member |
AS-38082-AMSIX | RADB | Lists AS8359 as a direct member |
AS-ANTALEX-V6 | RIPE | Lists AS8359 as a direct member |
AS-ANY2-RS | RADB | Lists AS8359 as a direct member |
AS-BLOCK-SET | RIPE | Lists AS8359 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS8359 as a direct member |
AS-CJSCPTK | RIPE | Lists AS8359 as a direct member |
AS-CWCCUSTOMERS | RIPE | Lists AS8359 as a direct member |
AS-DDITS:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS-DOCLER:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS-EMIX | RADB | Lists AS8359 as a direct member |
AS-GBLXEU | RIPE | Lists AS8359 as a direct member |
AS-GREEN-PEERS | RIPE | Lists AS8359 as a direct member |
AS-INN-TT-IN | RIPE | Lists AS8359 as a direct member |
AS-LIQUID-LINXPEERS | RIPE | Lists AS8359 as a direct member |
AS-MANDA-AMSIX-PEERS-V4 | RIPE | Lists AS8359 as a direct member |
AS-MANDA-AMSIX-PEERS-V6 | RIPE | Lists AS8359 as a direct member |
AS-MANDA-DECIX-PEERS-V4 | RIPE | Lists AS8359 as a direct member |
AS-MANDA-DECIX-PEERS-V6 | RIPE | Lists AS8359 as a direct member |
AS-MANDA-LINX-PEERS-V4 | RIPE | Lists AS8359 as a direct member |
AS-MANDA-LINX-PEERS-V6 | RIPE | Lists AS8359 as a direct member |
AS-MTU | RIPE | Lists AS8359 as a direct member |
AS-MTU-V6 | RIPE | Lists AS8359 as a direct member |
AS-MTU2 | RIPE | Lists AS8359 as a direct member |
AS-NAO-PEERS | RIPE | Lists AS8359 as a direct member |
AS-OPTILINK-RU | RIPE | Lists AS8359 as a direct member |
AS-PLUSNETUK:AS-LINX-PEERS-PRI | RIPE | Lists AS8359 as a direct member |
AS-RCN-CE-PEERS | RADB | Lists AS8359 as a direct member |
AS-RIS-RRC12 | RIPE | Lists AS8359 as a direct member |
AS-RIS-RRC13 | RIPE | Lists AS8359 as a direct member |
AS-ROSPRINT | RIPE | Lists AS8359 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS8359 as a direct member |
AS-SCARTEL-UPSTREAM | RIPE | Lists AS8359 as a direct member |
AS-SIDN-PEERS-AMSIX-V4 | RIPE | Lists AS8359 as a direct member |
AS-SIDN-PEERS-AMSIX-V6 | RIPE | Lists AS8359 as a direct member |
AS-STARLINE-V6 | RIPE | Lists AS8359 as a direct member |
AS-TELE-PLUS | RIPE | Lists AS8359 as a direct member |
AS-TITANDECIX | RIPE | Lists AS8359 as a direct member |
AS-TRUE:AS-EXCEPTIONS | RIPE | Lists AS8359 as a direct member |
AS-TSUAUA | RIPE | Lists AS8359 as a direct member |
AS-VTC | RIPE | Lists AS8359 as a direct member |
AS1200:AS-AMS-IX-PEERS | RIPE | Lists AS8359 as a direct member |
AS12703:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS16243:AS-PEERS-AMSIX | RIPE | Lists AS8359 as a direct member |
AS16347:AS-AMSIX-RS-EXCEPT | RIPE | Lists AS8359 as a direct member |
AS16559:AS-PEERS | RADB | Lists AS8359 as a direct member |
AS197068:AS-CUST | RIPE | Lists AS8359 as a direct member |
AS197068:AS-UPSTREAMS | RIPE | Lists AS8359 as a direct member |
AS199746:AS-BLACKLIST | RIPE | Lists AS8359 as a direct member |
AS204464:AS-BLACKLIST | RIPE | Lists AS8359 as a direct member |
AS20932:AS-PEERING | RIPE | Lists AS8359 as a direct member |
AS25091:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS25151:AS-AMS-IX-PEERS | RIPE | Lists AS8359 as a direct member |
AS2854:AS-AMS-IX-EXCEPTIONS | RIPE | Lists AS8359 as a direct member |
AS29075:AS-PEERS:AS-AMS-IX | RIPE | Lists AS8359 as a direct member |
AS29075:AS-PEERS:AS-LINX | RIPE | Lists AS8359 as a direct member |
AS31122:AS-ALL-PEERS | RIPE | Lists AS8359 as a direct member |
AS3267:AS-PROV | RIPE | Lists AS8359 as a direct member |
AS3303:AS-SWCMPEERS | RIPE | Lists AS8359 as a direct member |
AS34968:AS-AMS-IX-PEERS | RIPE | Lists AS8359 as a direct member |
AS34968:AS-AMS-IX-V6-PEERS | RIPE | Lists AS8359 as a direct member |
AS37271:AS-PEERS | RADB | Lists AS8359 as a direct member |
AS44291:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS49820:AS-AMS-IX-PEERS | RIPE | Lists AS8359 as a direct member |
AS51088:AS-PEERS-AMSIX | RIPE | Lists AS8359 as a direct member |
AS51202:AS-ALL | ALTDB | Lists AS8359 as a direct member |
AS61180:AS-PEERS-AMSIX | RIPE | Lists AS8359 as a direct member |
AS63034:AS-DECIX-NYC-CONNECTED | ARIN | Lists AS8359 as a direct member |
AS63034:AS-DECIX-NYC-RS | ARIN | Lists AS8359 as a direct member |
AS63034:AS-DECIX-NYC-RS-V6 | ARIN | Lists AS8359 as a direct member |
AS6695:AS-DECIX-FRA-CONNECTED | RIPE | Lists AS8359 as a direct member |
AS6695:AS-DECIX-FRA-RS | RIPE | Lists AS8359 as a direct member |
AS6695:AS-DECIX-FRA-RS-V6 | RIPE | Lists AS8359 as a direct member |
AS6777:AS-AMS-IX-RS | RIPE | Lists AS8359 as a direct member |
AS6777:AS-AMS-IX-RS-V6 | RIPE | Lists AS8359 as a direct member |
AS680:AS-AMSIX-RS-PEERS | RIPE | Lists AS8359 as a direct member |
AS6894:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS8218:AS-AMSIX-RS | RIPE | Lists AS8359 as a direct member |
AS8218:AS-PEERS | RIPE | Lists AS8359 as a direct member |
AS8308:AS-PEERINGS | RIPE | Lists AS8359 as a direct member |
AS8359:AS-UKRAINE | RIPE | Lists AS8359 as a direct member |
AS8359:AS-UKRAINE-V6 | RIPE | Lists AS8359 as a direct member |
AS9150:AS-PEERS-AMSIX | RIPE | Lists AS8359 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.