213.87.96.0/24
AS39811 · MTS PJSC
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
Russia
|
| Domain | mtsnet.ru |
| ASN | AS39811 |
| Parent Range | 213.87.0.0/16 |
| Registry | RIPE |
| ID | MTSNET-VLD |
WHOIS Details
inetnum: 213.87.96.0 - 213.87.97.255 netname: MTSNET-VLD descr: Vladivostok (Far East) division of Mobile Telesystems OJSC country: RU admin-c: PZ2049-RIPE admin-c: MTSA tech-c: PZ2049-RIPE status: ASSIGNED PA mnt-by: MR-DV-MTS-MNT mnt-by: MTU-NOC notify: [email protected] created: 2006-04-04T09:58:33Z last-modified: 2020-06-16T15:42:26Z source: RIPE abuse-email: [email protected] abuse-c: MAB8359-RIPE abuse-org: ORG-ZM1-RIPE role: MTSNET Administration address: MTS PJSC address: 4, Marksistskaya str., 109147 Moscow, Russia remarks: ************************************** remarks: Contact addresses: remarks: routing & peering [email protected] remarks: spam & security [email protected] remarks: mail [email protected] remarks: ddos reports [email protected] remarks: ************************************** mnt-by: MTSNET-MNT e-mail: [email protected] admin-c: YUF-RIPE tech-c: YUF-RIPE nic-hdl: MTSA created: 2004-04-03T10:05:17Z last-modified: 2019-05-29T08:19:05Z source: RIPE person: Black Hat address: Mobile TeleSystems PJSC address: Some street, 690000, Vladivostok City Russia phone: +7 914 703 87 38 nic-hdl: PZ2049-RIPE mnt-by: PZ630-MNT created: 2011-12-23T06:24:28Z last-modified: 2016-02-20T01:53:15Z source: RIPE route: 213.87.96.0/23 descr: Vladivostok (Far East) division of Mobile Telesystems OJSC origin: AS39811 mnt-by: MR-DV-MTS-MNT notify: [email protected] created: 2008-05-15T09:29:49Z last-modified: 2008-05-15T09:29:49Z source: RIPE route: 213.87.96.0/23 descr: Vladivostok (Far East) division of Mobile Telesystems PJSC origin: AS8359 mnt-by: MTU-NOC created: 2020-06-17T11:11:02Z last-modified: 2020-06-17T11:13:30Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 213.87.96.0/24
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 213.87.0.0/16 | AS8359 | MTS PJSC | 65,536 |
Nearby Ranges
BGP prefixes that overlap with 213.87.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 213.87.0.0/16 | AS8359 | MTS PJSC | 65,536 |
| 213.87.128.0/19 | AS8359 | Mobile subscribers pool | 8,192 |
| 213.87.80.0/20 | AS8359 | Mobile subscribers pool | 4,096 |
| 213.87.192.0/21 | AS42115 | MTSNET infra in Ufa | 2,048 |
| 213.87.248.0/22 | AS8359 | MTSNET gprs-infra in Ural | 1,024 |
| 213.87.240.0/22 | AS8359 | Mobile subscribers pool | 1,024 |
| 213.87.160.0/22 | AS8359 | Mobile subscribers pool | 1,024 |
| 213.87.76.0/23 | AS8359 | Ekaterinburg (Ural) division of Mobile Telesystems OJSC | 512 |
| 213.87.42.0/23 | AS15640 | Mobile Telesystems PJSC | 512 |
| 213.87.98.0/23 | AS8359 | Vladivostok (Far East) division of Mobile Telesystems OJSC | 512 |
| 213.87.116.0/23 | AS28884 | MTSNET infra in Siberia | 512 |
| 213.87.124.0/23 | AS28884 | MR-SIB-MTS infra in Siberia, Norilsk | 512 |
| 213.87.106.0/23 | AS8359 | Vladivostok division of Mobile Telesystems OJSC | 512 |
| 213.87.208.0/23 | AS8359 | MTSNET SPB infra | 512 |
| 213.87.244.0/23 | AS8359 | MTSNET gprs-infra in Ural | 512 |
| 213.87.70.0/23 | AS8359 | MTSNET infrastructure in N.Novgorod | 512 |
Hosted domains
There are 2 domain names hosted across 2 IP addresses on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|---|---|
| 213.87.96.14 | xjkjlbkmybr.online | 1 |
| 213.87.96.208 | amurgpz.ru | 1 |
Hosted domains API
Pingable IPs
83 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 213.87.96.118 |
9.60ms from Khabarovsk,
RU
|
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 174.108.77.56 |
4.70ms from Charlotte,
US
|
|
| 191.187.233.104 |
7.87ms from Curitiba,
BR
|
|
| 172.215.202.136 |
3.40ms from Denver,
US
|
|
| 1.190.94.120 |
8.70ms from Harbin,
CN
|
|
| 80.69.171.200 |
0.90ms from Helsinki,
FI
|
|
| 185.85.186.104 |
0.84ms from London,
GB
|
|
| 86.154.78.152 |
6.26ms from London,
GB
|
|
| 120.242.29.184 |
8.06ms from Nanjing,
CN
|
|
| 101.66.35.88 |
11.91ms from Ningbo,
CN
|
|
| 174.56.147.8 |
14.68ms from Orlando,
US
|
|
| 219.165.115.56 |
4.57ms from Osaka,
JP
|
|
| 177.60.210.88 |
16.71ms from Osasco,
BR
|
|
| 80.213.143.184 |
5.55ms from Oslo,
NO
|
|
| 78.201.147.24 |
1.20ms from Paris,
FR
|
|
| 203.227.202.8 |
7.88ms from Seoul,
KR
|
|
| 211.205.217.232 |
1.83ms from Seoul,
KR
|
|
| 210.71.253.56 |
1.35ms from Taipei,
TW
|
|
| 171.126.202.56 |
7.95ms from Taiyuan,
CN
|
|
| 141.28.237.104 |
6.18ms from Zuerich,
CH
|
|
| 87.203.240.200 |
1.28ms from Athens,
GR
|
|
| 47.109.41.168 |
0.52ms from Chengdu,
CN
|
|
| 182.142.53.248 |
6.42ms from Chengdu,
CN
|
|
| 175.44.183.8 |
12.46ms from Nanchang,
CN
|
|
| 125.207.176.232 |
9.69ms from Osaka,
JP
|
|
| 78.192.29.56 |
1.25ms from Paris,
FR
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all toolsSummarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs