Routing security
AS60490 MTS-CLOUD MTS PJSC
Unclassified RIPE
RPKI valid
32%
23 of 71 announcements
RPKI invalid
0
none
No ROA
48
not covered by any ROA
IRR registered
99%
1 missing · 0 other origin
ROAs
32
authorising this AS
Announcements
What this network originates
Every prefix observed with AS60490 as its origin, checked against RPKI and the IRR. Problems sort first.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS60490 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 62.113.66.0/24 | /24 | RIPENCC |
| 62.113.67.0/24 | /24 | RIPENCC |
| 62.113.71.0/24 | /24 | RIPENCC |
| 62.113.72.0/24 | /24 | RIPENCC |
| 62.113.73.0/24 | /24 | RIPENCC |
| 62.113.76.0/24 | /24 | RIPENCC |
| 62.113.78.0/23 | /23 | RIPENCC |
| 91.185.81.0/24 | /24 | RIPENCC |
| 91.185.88.0/24 | /24 | RIPENCC |
| 91.185.90.0/24 | /24 | RIPENCC |
| 91.185.95.0/24 | /24 | RIPENCC |
| 91.236.180.0/24 | /24 | RIPENCC |
| 93.159.220.0/24 | /24 | RIPENCC |
| 111.88.160.0/24 | /24 | RIPENCC |
| 111.88.161.0/24 | /24 | RIPENCC |
| 111.88.162.0/24 | /24 | RIPENCC |
| 111.88.163.0/24 | /24 | RIPENCC |
| 176.109.64.0/23 | /23 | RIPENCC |
| 176.109.64.0/24 | /24 | RIPENCC |
| 176.109.65.0/24 | /24 | RIPENCC |
| 176.109.67.0/24 | /24 | RIPENCC |
| 176.109.70.0/24 | /24 | RIPENCC |
| 176.109.80.0/24 | /24 | RIPENCC |
| 178.236.19.0/24 | /24 | RIPENCC |
| 178.236.25.0/24 | /24 | RIPENCC |
| 194.150.88.0/24 | /24 | RIPENCC |
| 194.150.89.0/24 | /24 | RIPENCC |
| 194.150.90.0/24 | /24 | RIPENCC |
| 194.150.91.0/24 | /24 | RIPENCC |
| 2a02:28:7::/48 | /48 | RIPENCC |
| 2a02:2a:1000::/36 | /48 | RIPENCC |
| 2a02:2a:1000::/41 | /41 | 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 AS60490 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 |
|---|---|---|---|---|---|
| 62.113.64.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-06-29 | Not announced |
| 62.113.65.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-07-15 | Not announced |
| 62.113.69.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-07-02 | Not announced |
| 77.105.176.0/20 | RIPE | — | MNT-CLOUDMTS | 2022-05-19 | Not announced |
| 77.105.184.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-05-15 | Not announced |
| 89.22.160.0/22 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.160.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.161.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.162.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.163.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.164.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Not announced |
| 89.22.165.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Not announced |
| 89.22.168.0/22 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Not announced |
| 89.22.170.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Not announced |
| 89.22.171.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Not announced |
| 89.22.172.0/23 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.172.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.173.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.180.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.181.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.182.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.183.0/24 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Not announced |
| 89.22.184.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Not announced |
| 91.185.80.0/20 | RIPE | — | MNT-CLOUDMTS | 2021-08-31 | Not announced |
| 91.185.82.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-08-30 | Not announced |
| 91.185.83.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-07-13 | Not announced |
| 91.185.87.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-05-19 | Not announced |
| 91.185.92.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-05-04 | Not announced |
| 91.185.94.0/23 | RIPE | — | MNT-CLOUDMTS | 2022-12-02 | Not announced |
| 94.125.189.0/24 | RIPE | — | MNT-IT-GRAD | 2026-08-10 | Not announced |
| 111.88.161.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-07-21 | Not announced |
| 111.88.163.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-08-06 | Not announced |
| 176.109.66.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-08-29 | Not announced |
| 176.109.67.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-08-29 | Not announced |
| 176.109.72.0/22 | RIPE | — | MNT-CLOUDMTS | 2024-02-02 | Not announced |
| 176.109.76.0/22 | RIPE | — | MNT-CLOUDMTS | 2024-02-27 | Not announced |
| 176.109.79.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-01-30 | Not announced |
| 176.109.80.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-03-22 | Not announced |
| 176.109.82.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-04-26 | Not announced |
| 176.109.84.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-10-08 | Not announced |
| 176.109.91.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-11-12 | Not announced |
| 176.109.92.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-10-11 | Not announced |
| 176.109.93.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-10-11 | Not announced |
| 176.109.94.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-12-03 | Not announced |
| 176.118.20.0/22 | RIPE | MTS Cloud network | MTU-NOC | 2019-02-19 | Not announced |
| 176.118.28.0/22 | RIPE | MTS PJSC | MTU-NOC | 2022-09-18 | Not announced |
| 176.118.28.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-09-18 | Not announced |
| 178.236.24.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-05-28 | Not announced |
| 178.236.25.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-06-20 | Not announced |
| 185.47.36.0/24 | RIPE | — | GG9306-MNT | 2020-09-23 | Not announced |
| 185.47.37.0/24 | RIPE | — | GG9306-MNT | 2020-09-23 | Not announced |
| 185.47.38.0/24 | RIPE | — | GG9306-MNT | 2020-09-23 | Not announced |
| 185.47.39.0/24 | RIPE | — | GG9306-MNT | 2020-09-23 | Not announced |
| 185.59.138.0/23 | RIPE | MTS PJSC | MTU-NOC | 2020-10-02 | Not announced |
| 188.93.48.0/21 | RIPE | — | MNT-CLOUDMTS | 2024-07-23 | Not announced |
| 188.93.48.0/24 | RIPE | — | MNT-IT-GRAD | 2025-07-16 | Not announced |
| 188.93.50.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-04-02 | Not announced |
| 188.93.51.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-05-23 | Not announced |
| 193.8.208.0/22 | RIPE | MTS PJSC | MTU-NOC | 2025-03-10 | Not announced |
| 194.150.88.0/22 | RIPE | — | MNT-CLOUDMTS | 2021-10-27 | Not announced |
| 212.109.207.0/24 | RIPE | MTS PJSC | MTU-NOC | 2023-09-22 | Not announced |
| 212.109.214.0/23 | RIPE | MTS PJSC | MTU-NOC | 2025-07-18 | Not announced |
| 213.108.128.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-09-18 | Not announced |
| 213.108.129.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-09-18 | Not announced |
| 2a02:2a:1000::/36 | RIPE | # CloudMTS ipv6 | MTU-NOC | 2025-06-27 | Not announced |
| 2a02:2a:1101::/48 | RIPE | — | MNT-CLOUDMTS | 2025-06-27 | Not announced |
| 62.113.66.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-06-24 | Announced |
| 62.113.67.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-06-27 | Announced |
| 62.113.68.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-06-27 | Announced |
| 62.113.71.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-07-16 | Announced |
| 62.113.72.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-07-16 | Announced |
| 62.113.73.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-03-12 | Announced |
| 62.113.74.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-11-13 | Announced |
| 62.113.76.0/24 | RIPE | MTS Web Services | MTU-NOC | 2026-10-07 | Announced |
| 62.113.78.0/23 | RIPE | MTS WebServices PJSC | MTU-NOC | 2026-06-11 | Announced |
| 77.105.177.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-11-16 | Announced |
| 77.105.178.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-11-26 | Announced |
| 77.105.179.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-12-28 | Announced |
| 77.105.180.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-01-12 | Announced |
| 77.105.182.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-03-13 | Announced |
| 77.105.185.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-04-09 | Announced |
| 77.105.186.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-04-12 | Announced |
| 77.105.190.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-06-29 | Announced |
| 77.105.191.0/24 | RIPE | — | MNT-CLOUDMTS | 2023-12-01 | Announced |
| 89.22.164.0/23 | RIPE | MTS PJSC | MNT-CLOUDMTS | 2020-09-07 | Announced |
| 89.22.168.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Announced |
| 89.22.169.0/24 | RIPE | — | MNT-CLOUDMTS | 2020-09-14 | Announced |
| 89.22.180.0/22 | RIPE | MTS PJSC | MTU-NOC | 2020-06-15 | Announced |
| 89.22.184.0/22 | RIPE | MTS Cloud network | MTU-NOC | 2025-03-12 | Announced |
| 91.185.81.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.84.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.85.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.86.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.88.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.90.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 91.185.91.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-05-23 | Announced |
| 91.185.92.0/23 | RIPE | — | MNT-CLOUDMTS | 2024-04-16 | Announced |
| 91.185.93.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-05-04 | Announced |
| 91.185.94.0/24 | RIPE | — | MNT-CLOUDMTS | 2022-12-02 | Announced |
| 91.185.95.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-11-19 | Announced |
| 91.236.180.0/24 | RIPE | — | RU-1CLOUD-1-MNT | 2026-10-27 | Announced |
| 93.159.220.0/24 | RIPE | — | RU-1CLOUD-1-MNT | 2026-10-15 | Announced |
| 111.88.160.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-07-09 | Announced |
| 111.88.162.0/24 | RIPE | — | MNT-CLOUDMTS | 2026-07-21 | Announced |
| 176.109.64.0/23 | RIPE | — | MNT-CLOUDMTS | 2024-04-16 | Announced |
| 176.109.72.0/21 | RIPE | — | MNT-CLOUDMTS | 2024-02-27 | Announced |
| 176.109.83.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-05-28 | Announced |
| 176.109.85.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-10-01 | Announced |
| 176.109.86.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-11-08 | Announced |
| 176.109.87.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-11-21 | Announced |
| 176.109.88.0/23 | RIPE | — | MNT-CLOUDMTS | 2024-10-08 | Announced |
| 176.109.90.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-10-08 | Announced |
| 176.109.95.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-12-03 | Announced |
| 178.236.18.0/24 | RIPE | — | MNT-CLOUDMTS | 2024-12-20 | Announced |
| 178.236.19.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-02-24 | Announced |
| 178.236.22.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-01-22 | Announced |
| 178.236.23.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-02-17 | Announced |
| 185.47.36.0/22 | RIPE | — | GG9306-MNT | 2020-09-23 | Announced |
| 188.93.49.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-25 | Announced |
| 193.8.208.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-10 | Announced |
| 193.8.209.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-10 | Announced |
| 193.8.210.0/24 | RIPE | — | MNT-CLOUDMTS | 2025-03-12 | Announced |
| 194.113.236.0/23 | RIPE | MTS PJSC | MTU-NOC | 2020-12-08 | Announced |
| 194.150.88.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-10-27 | Announced |
| 194.150.89.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-10-27 | Announced |
| 194.150.90.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-10-27 | Announced |
| 194.150.91.0/24 | RIPE | — | MNT-CLOUDMTS | 2021-10-27 | Announced |
| 212.6.56.0/24 | RIPE | — | MNT-RU-INNOSETI-1 | 2020-07-17 | Announced |
| 2a02:28:7::/48 | RIPE | MTS Cloud Devision | COMSTAR-MNT | 2020-08-25 | Announced |
| 2a02:2a:1000::/41 | RIPE | #CloudMTS ipv6 | MTU-NOC | 2024-03-04 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS60490 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS60490 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS60490 as a direct member |
AS-CLOUDMTS | RIPE | Lists AS60490 as a direct member |
AS-CTSRND | RIPE | Lists AS60490 as a direct member |
AS-EMIX | RADB | Lists AS60490 as a direct member |
AS-MTU | RIPE | Lists AS60490 as a direct member |
AS-MTU2 | RIPE | Lists AS60490 as a direct member |
AS-SERVICEPIPE | RIPE | Lists AS60490 as a direct member |
AS197068:AS-CUST | RIPE | Lists AS60490 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS60490 as a direct member |
RPKI from rpki-client, validated 2026-11-02 13:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-02. Cross-check on bgp.he.net.