Ready to eliminate fraud?
Start fighting fraud in minutes!
Questions? Call us at (800) 713-2618
Schedule a Demo Sign Up »Get Started with 5,000 Free Lookups Per Month!
AS8359 MTS PJSC Network Details
AS8359 is an autonomous system number (ASN) managed by MTS PJSC. The registry was last assigned on 17 Sep 2002 with 3.2502309159569E+30 IP addresses active in the network. AS8359 network's IP addresses are assigned by Réseaux IP Européens (RIPE), the regional internet registry (RIR) for European IP addresses.
A sample hostname from the network is available at a23-199-88-0.deploy.static.akamaitechnologies.com (5.144.96.0). Average ping response times for the MTS PJSC network are 151.69 milliseconds. Based on our research of active subnet ranges, there are 3.2502309159569E+30 IPv6 addresses and 2,412,988 IPv4 addresses assigned to MTS PJSC.
AS8359 Network Report
Lookup details for the MTS PJSC network.
| Network Name | AS8359 MTS PJSC |
|---|---|
| Network ISP | Mobile TeleSystems PJSC |
| Network Organization | OJSC "Mobile TeleSystems" |
| Registry Status | Active — Allocated under RIPE |
| Registry Date | 17 Sep 2002 |
| Total IPv4 Addresses | 2,412,988 |
| Total IPv6 Addresses | 3.2502309159569E+30 |
Live IP Address Intelligence API
Access the best IP reputation data to serve everything you need about IP addresses for any region of the world. Retrieve accurate geographic details, ASN network data, and the industry's leading risk analysis for proxy & VPN detection and abusive behavior. Test it with a free account.
View API Docs » — OR — Grab a Free Account »
AS8359 IPv4 Address Subnets
| 5.144.96.0/19 |
|
St Petersburg, St.-Petersburg | Mobile TeleSystems PJSC | OJSC "Mobile TeleSystems" |
|---|---|---|---|---|
| 23.199.88.0/23 |
|
Novosibirsk, Novosibirsk Oblast | Akamai Technologies | Akamai International, BV |
| 23.199.90.0/23 |
|
Ekaterinburg, Sverdlovsk | Akamai Technologies | Akamai International, BV |
| 62.5.128.0/17 |
|
Moscow, Moscow | PTTNET's first | |
| 62.113.88.0/24 |
|
Nizhniy Sayantuy, Buryatiya Republic | Mts Pjsc | |
| 62.118.0.0/16 |
|
Moscow, Moscow | ZAO MTU-Intel's Moscow Region | ZAO "CentrTorg Sbyt" |
| 62.118.67.0/24 |
|
St Petersburg, St.-Petersburg | Mts Pjsc | MTS Spb |
| 62.152.64.0/19 |
|
St Petersburg, St.-Petersburg | Mobile TeleSystems PJSC | OJSC "Mobile TeleSystems" |
| 62.220.43.0/24 |
|
Nizhny Novgorod, Nizhny Novgorod Oblast | Stream network | JSC Comstar-Region |
| 80.83.234.0/25 |
|
Khor, Khabarovsk | Mobile TeleSystems | Vladivostok (Far East) division of |
| 80.83.234.128/25 |
|
Khabarovsk, Khabarovsk | Mobile TeleSystems | Vladivostok (Far East) division of |
| 80.83.238.0/25 |
|
Partizansk, Primorskiy (Maritime) Kray | Mobile TeleSystems | Vladivostok (Far East) division of |
| 80.83.239.0/25 |
|
Khabarovsk, Khabarovsk | Mobile TeleSystems | Vladivostok (Far East) division of |
| 81.177.72.0/21 |
|
Moscow, Moscow | Mts Pjsc | Mobile TeleSystems PJSC |
| 81.195.0.0/16 |
|
Moscow, Moscow | ZAO MTU-Intel's Moscow Region | ZAO MTU-Intel |
| 81.195.236.0/24 |
|
St Petersburg, St.-Petersburg | Mts Pjsc | Mts M2M |
| 81.201.16.0/20 |
|
St Petersburg, St.-Petersburg | OJSC "Mobile TeleSystems" | |
| 82.96.192.0/18 |
|
St Petersburg, St.-Petersburg | Mts Pjsc | MTS reserved p2p |
| 82.204.128.0/17 |
|
Moscow, Moscow | Mts Pjsc | Mobile TeleSystems PJSC |
| 83.136.24.0/21 |
|
Moscow, Moscow | MTU-Inform's Moscow Region Network | MTU-Inform company |
| 83.237.0.0/16 |
|
Moscow, Moscow | ZAO MTU-Intel's Moscow Region | ZAO MTU-Intel |
| 83.242.128.0/17 |
|
Moscow, Moscow | Mobile TeleSystems PJSC | COMSTAR Telecommunications |
| 83.242.224.0/21 |
|
Moscow, Moscow | Comstar Saint-Petersburg | |
| 84.17.0.0/19 |
|
St Petersburg, St.-Petersburg | Mts Pjsc | Mts Spb |
| 85.140.0.0/15 |
|
Samara, Samara Oblast | Mts Pjsc | Mtsgprs |
| 85.140.0.0/21 |
|
Samara, Samara Oblast | Mts Pjsc | Mtsgprs |
| 85.140.12.0/22 |
|
Ekaterinburg, Sverdlovsk | Mts Pjsc | Mobile TeleSystems PJSC / former |
| 85.140.16.0/21 |
|
Solikamsk, Perm | Mts Pjsc | Mobile TeleSystems PJSC / former |
| 85.140.24.0/22 |
|
Ekaterinburg, Sverdlovsk | Mts Pjsc | Mobile TeleSystems PJSC / former |
| 85.140.31.0/24 |
|
St Petersburg, St.-Petersburg | Mts Pjsc | Mobile TeleSystems PJSC / former |
| 85.140.76.0/22 |
|
Ekaterinburg, Sverdlovsk | MTS gprs-infra in Ural-region | PJSC MTS / former CJSC |
| 85.235.160.0/19 |
|
Moscow, Moscow | Mts Pjsc | |
| 89.22.188.0/23 |
|
Moscow, Moscow | Mts Pjsc | MTS Cheboksary |
| 89.175.0.0/16 |
|
Moscow, Moscow | Mobile TeleSystems PJSC | OOO "Fitness System" |
| 89.175.248.0/21 |
|
Moscow, Moscow | Mobile TeleSystems PJSC | CJSC "Nevaline" |
| 89.209.0.0/16 |
|
Kolomyia, Ivano-Frankivsk | Tsua |
show more..
AS8359 IPv6 Address Subnets
| 2a00:f00::/32 |
|
St Petersburg, St.-Petersburg | Mts-Spb | Lanck Telecom, Ltd. |
|---|---|---|---|---|
| 2a00:1fa0::/29 |
|
Moscow, Moscow | Mts Pjsc | MTS Mobile Moscow and Center |
| 2a00:1fa0::/33 |
|
Moscow, Moscow | Mts Pjsc | MTS Mobile Moscow and Center |
| 2a00:1fa0:8000::/33 |
|
Moscow, Moscow | Mts Pjsc | MTS Mobile North-West |
| 2a00:1fa2::/33 |
|
Chelyabinsk, Chelyabinsk | Mts Pjsc | MTS Mobile Ural |
| 2a00:1fa3::/64 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:200::/40 |
|
Blagoveshchensk, Amur Oblast | Mts Pjsc | MTS Far East |
| 2a00:1fa3:200::/49 |
|
Blagoveshchensk, Amur Oblast | Mts Pjsc | MTS Far East |
| 2a00:1fa3:200:8000::/49 |
|
Blagoveshchensk, Amur Oblast | Mts Pjsc | MTS Far East |
| 2a00:1fa3:201::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:201:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:202::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:202:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:203::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:203:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:204::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:204:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:205::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:205:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:206::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:206:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:207::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:207:8000::/49 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:500::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:510::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:520::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:530::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:540::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:550::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:560::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:570::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:600::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:610::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:620::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:630::/44 |
|
Khabarovsk, Khabarovsk | Mts Pjsc | MTS Far East |
| 2a00:1fa3:640::/44 |
|
Tynda, Amur Oblast | Mts Pjsc | MTS Far East |
show more..
Network Latency Stats
Based on testing from worldwide server locations, average response time has been rated as moderate at 151.69 milliseconds.
What is an Autonomous System (AS)?
Autonomous System (AS) numbers group IP address networks and routing prefixes with the same external routing protocols. For example, all IP addresses managed by an organization are typically listed in the same AS network group. This could include all IP address prefixes managed by a university, corporate entity, internet service provider, or similar organization. Autonomous systems are useful for organizing the internet's IP addresses by the administrative entities which manage each IP address subnet. If an organization has multiple routing policies then a unique AS number will be assigned to each group of IP addresses.
Looking for IP Address Data?
Tap into over 10 years of IP address technology and data solutions for geographic locations, proxy detection, risk analysis, bot analysis, and much more. Get data straight to your site or app with our APIs, JavaScript filters, and database products.
Recent IP Address Reports
Questions About IPQS?
Chat with our fraud prevention experts.
Get a Free API Key — OR — Contact Us »