AS13174 MTSNet MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
Moscow, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
12total
12 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)12,032
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)12|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 12
1 / 2
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.216.167.0/24 | 🇷🇺 RU | RIPENCC | assigned |
| 194.54.148.0/22 | 🇷🇺 RU | RIPENCC | assigned |
| 213.87.44.0/22 | 🇷🇺 RU | RIPE | assigned |
All 12 announced prefixes of AS13174 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS13174 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC12
ASPA
No ASPA
Abuse Contact
+31205354444
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS13174 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/13174Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/13174" | jq