MTS IP Ranges
MTS is the fixed and mobile operator run by Mobile TeleSystems PJSC of Moscow. AS8359 carries the bare as-name MTS in the RIPE database, under organisation record ORG-ZM1-RIPE, and its aut-num object was created there on 17 September 2002. That organisation record holds ninety-six aut-num objects in all, from SPBMTS-AS in St Petersburg through MTS-KAZAN-AS and the older COMSTAR-AS to MTS-CLOUD, so AS8359 is the flagship network rather than the whole company.
- Provider
- MTS
- Primary ASN
- AS8359
- Category
- ISP
- Headquarters
- Moscow, Russia
- Announced IPv4 prefixes
- 421
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS8359 (MTS MTS PJSC). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
85.140.0.0/15
91.78.0.0/15
89.175.0.0/16
91.76.0.0/16
213.87.0.0/16
91.77.0.0/16
83.237.0.0/16
81.195.0.0/16
62.118.0.0/16
178.141.0.0/16
2a12:3d40::/29
2a02:28::/29
2a00:1fa0::/30 (IPv6)
What does an MTS IP mean in a privacy test?
An address on AS8359 is a Russian line answering for itself, but how much more you can read off it depends entirely on which MTS block it sits in. Inside 213.87.0.0/16 the reverse names are unusually explicit about service type: thirty-two of thirty-three addresses sampled for this page answered, in forms such as 85.gprs.mts.ru for mobile packet data, 15.15.static-ip.mts.ru for a fixed static assignment, and 25-25-customer.vladimir.mtsnet.ru naming the city outright. Inside 178.141.0.0/16 the names say dynamic-pppoe and kirov and little else. Across nine of the other large blocks, among them 85.140, 89.175, 83.237 and 62.118, twenty-nine sampled addresses returned no reverse name at all, so there the RIPE inetnum is the only thing left to read. The trap runs the other way too: because ninety-six autonomous systems share the MTS organisation record, a lookup that comes back as something other than AS8359 has not ruled MTS out.
The geofeed MTS declares and the as-set peers filter on
MTS does declare a geofeed, and it is easy to miss because it is not an attribute. The AS8359 aut-num object carries the free-text line remarks: geofeed https://lg.mtu.ru/geofeed.csv, repeated twice, which is the RFC 8805 pointer a geolocation database would follow. It could not be followed for this page: lg.mtu.ru failed to resolve on every attempt, so the declaration exists and the file behind it did not answer. None of the MTS inetnums checked carried a geofeed: attribute of their own either, so to place an MTS address you are back to the per-block description in the registry.
What does answer is the routing side. The as-set AS-MTU, described in the RIPE database as the ASes for MTS customers, lists 835 members with AS8359 first among them, and AS-MTU-V6 is its IPv6 counterpart. MTS names both in its own PeeringDB record, which sets peering policy to selective and traffic ratio to balanced. Those two object names, not the ASN, are what a peer builds prefix lists from, which is why the customer networks sitting behind MTS are visible in the set and invisible in a plain AS8359 lookup.
Subscriber line, mobile core, or MTS infrastructure
The registry has a purpose-built marker for this and MTS uses it. The inetnum covering 213.87.200.0 - 213.87.207.255 is netname MTSNET-MSK, described as MTS IT infrastructure, and it carries remarks: INFRA-AW, the value RIPE policy document ripe-530 requires on an assignment an LIR has made to its own infrastructure. The Kirov subscriber block 178.141.56.0 - 178.141.63.255, netname MTS-KRV-PPPOE-8-NET and described as dynamic PPPoE individual customers, has no such remark. Both objects carry status: ASSIGNED PA, so the status field will not separate them; the remark and the netname will.
Where reverse DNS exists it is a type field rather than decoration, and the word in the label is what matters. Sampling for this page found gprs.mts.ru and mobile.sib.mts.ru on mobile addresses, static-ip.mts.ru on fixed static ones, dynamic-pppoe names under kirov.pv.mts.ru on the Kirov pool, and infrastructure-35-35.mtsnet.ru on MTS equipment. Do not try to parse the digits: 213.87.50.60 answers as 60.50.mts.ru with the last two octets swapped, while 213.87.120.30 answers as 213-87-120-30.mobile.sib.mts.ru in order. One sampled address in the Moscow space returned a customer's own domain instead of an MTS name, so a non-MTS hostname inside AS8359 means a delegated block, not a mislabelled one.
Related tools
Frequently asked questions
Does MTS publish a geofeed?
Yes, but only as a pointer, and it did not answer. The AS8359 aut-num object in the RIPE database carries a remarks line reading geofeed https://lg.mtu.ru/geofeed.csv. When that URL was tested for this page the host lg.mtu.ru failed to resolve, so the file could not be retrieved. Treat the declaration as present and the data as unavailable, and use the per-block description in the RIPE inetnum instead.
How many autonomous systems are registered to MTS?
Ninety-six aut-num objects carry the MTS organisation record ORG-ZM1-RIPE. AS8359 is the one with the plain as-name MTS; the same organisation also holds AS29209 SPBMTS-AS, AS29225 MTS-KAZAN-AS, the older AS6731 COMSTAR-AS, and service networks including AS60490 MTS-CLOUD and AS44731 MWS.
What do gprs and mobile mean in an MTS hostname?
Those labels mark MTS mobile addresses. Sampling inside 213.87.0.0/16 for this page returned names such as 85.gprs.mts.ru and 130.gprs.mts.ru, and 213-87-120-30.mobile.sib.mts.ru where sib is the Siberian region. An address carrying one of those is a handset or a mobile data session rather than a fixed line.
Why does an MTS address often have no reverse DNS name?
Because coverage is uneven by block rather than thin overall. Twenty-nine addresses sampled across nine of the larger MTS blocks, among them 85.140, 89.175, 83.237 and 62.118, returned nothing at all, while 213.87.0.0/16 answered on thirty-two of thirty-three sampled. The absence of a hostname tells you which part of the network you are in and nothing more.
How do I tell MTS infrastructure from a subscriber address?
Read the covering RIPE inetnum for the INFRA-AW remark. RIPE policy document ripe-530 requires that value on address space an LIR assigns to its own infrastructure, and the MTSNET-MSK block described as MTS IT infrastructure carries it while the Kirov PPPoE customer block does not. Reverse DNS backs it up: a name like infrastructure-35-35.mtsnet.ru is MTS equipment, and a dynamic-pppoe name is a subscriber router.