AS41822
MTS PJSC · mts.ru
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›IP Ranges
| Netblock | Company | Num of IPs |
|---|---|---|
| 46.250.64.0/21 | JSC Regional Technical Centre | 2,048 |
| 92.246.192.0/21 | JSC Regional Technical Centre | 2,048 |
| 109.198.64.0/21 | PJSC MTS | 2,048 |
| 46.250.72.0/22 | JSC Regional Technical Centre | 1,024 |
| 46.250.84.0/22 | JSC Regional Technical Centre | 1,024 |
| 46.250.88.0/22 | JSC Regional Technical Centre | 1,024 |
| 46.250.92.0/22 | JSC Regional Technical Centre | 1,024 |
| 91.143.48.0/22 | PJSC MTS branch Ural | 1,024 |
| 91.143.52.0/22 | PJSC MTS branch Ural | 1,024 |
| 91.143.56.0/22 | PJSC MTS branch Ural | 1,024 |
| 92.246.192.0/22 | JSC Regional Technical Centre | 1,024 |
| 92.246.196.0/22 | JSC Regional Technical Centre | 1,024 |
| 92.246.208.0/22 | JSC Regional Technical Centre | 1,024 |
| 94.125.240.0/22 | PJSC MTS | 1,024 |
| 178.72.84.0/22 | JSC Regional Technical Centre | 1,024 |
| 178.72.100.0/22 | JSC Regional Technical Centre | 1,024 |
| 37.208.100.0/23 | JSC Regional Technical Centre | 512 |
| 37.208.102.0/23 | JSC Regional Technical Centre | 512 |
| 46.250.78.0/23 | JSC Regional Technical Centre | 512 |
| 91.143.58.0/23 | PJSC MTS branch Ural | 512 |
| 92.246.214.0/23 | PJSC MTS | 512 |
| 94.125.244.0/23 | PJSC MTS | 512 |
| 94.125.246.0/23 | PJSC MTS | 512 |
| 178.72.92.0/23 | JSC Regional Technical Centre | 512 |
| 91.143.51.0/24 | PJSC MTS branch Ural | 256 |
| 91.143.52.0/24 | PJSC MTS branch Ural | 256 |
| 91.143.53.0/24 | PJSC MTS branch Ural | 256 |
| 91.143.54.0/24 | PJSC MTS branch Ural | 256 |
| 91.143.55.0/24 | Nefteyuganskoe rajonnoe municipalnoe predpriyatie | 256 |
| 91.143.62.0/24 | PJSC MTS branch Ural | 256 |
| 92.246.212.0/24 | PJSC MTS | 256 |
| 92.246.213.0/24 | PJSC MTS | 256 |
| 176.222.18.0/24 | Ural Branch of CJSC COMSTAR-Regions in Surgut | 256 |
| 178.72.94.0/24 | JSC Regional Technical Centre | 256 |
| 178.72.95.0/24 | JSC Regional Technical Centre | 256 |
There are no known IPv6 addresses belonging to this network
WHOIS Details
ASHandle: AS41822
OrgID: AS41822
ASName: AS41822
ASNumber: AS41822
RegDate: 0000-00-00
Updated: 0000-00-00
TechHandle: AA00-AAAA
Source: AAAA
Hosted Domains
There are 22 domain names hosted across 19 IP addresses on this ASN.
| IP Address | Domain | Domains on this IP |
|---|---|---|
| 91.143.50.76 | ██████████ | 4 |
| 178.72.95.87 | ███████ | 1 |
| 91.143.50.59 | ████████ | 1 |
| 91.143.58.210 | ██████████ | 1 |
| 94.125.244.12 | ████████ | 1 |
| 91.143.55.43 | ██████████ | 1 |
| 91.143.62.161 | ███████ | 1 |
| 91.143.50.222 | ██████████ | 1 |
| 91.143.62.125 | █████████ | 1 |
| 91.143.58.10 | █████████ | 1 |
Peers
There are 3 peers for this ASN.
Upstreams
There is 1 peer for this ASN.
| upstreams | Name |
|---|---|
| AS8359 | MTS PJSC |
Downstreams
There are 2 downstreams for this ASN.
Pingable IPs
52 IPs in this ASN replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 91.143.55.44 |
17.27ms from Yekaterinburg,
RU
|
|
| 37.208.100.1 |
16.26ms from Yekaterinburg,
RU
|
|
| 46.250.84.2 |
16.17ms from Yekaterinburg,
RU
|
|
| 91.143.59.213 |
16.20ms from Yekaterinburg,
RU
|
|
| 91.143.53.241 |
17.25ms from Yekaterinburg,
RU
|
|
| 178.72.93.180 |
16.58ms from Yekaterinburg,
RU
|
|
| 178.72.92.209 |
16.57ms from Yekaterinburg,
RU
|
|
| 94.125.244.33 |
18.79ms from Yekaterinburg,
RU
|
|
| 92.246.211.173 |
16.82ms from Yekaterinburg,
RU
|
|
| 46.250.69.105 |
16.59ms from Yekaterinburg,
RU
|
|
| 92.246.209.200 |
16.72ms from Yekaterinburg,
RU
|
|
| 92.246.199.148 |
18.52ms from Yekaterinburg,
RU
|
|
| 178.72.100.65 |
18.84ms from Yekaterinburg,
RU
|
|
| 178.72.101.129 |
18.77ms from Yekaterinburg,
RU
|
|
| 91.143.54.253 |
17.28ms from Yekaterinburg,
RU
|
|
| 91.143.50.225 |
15.89ms from Yekaterinburg,
RU
|
|
| 46.250.92.204 |
16.51ms from Yekaterinburg,
RU
|
|
| 94.125.240.253 |
15.67ms from Yekaterinburg,
RU
|
|
| 46.250.93.25 |
16.63ms from Yekaterinburg,
RU
|
|
| 178.72.94.129 |
16.21ms from Yekaterinburg,
RU
|
|
| 46.250.64.10 |
16.43ms from Yekaterinburg,
RU
|
|
| 178.72.95.81 |
16.22ms from Yekaterinburg,
RU
|
|
| 46.250.66.228 |
16.65ms from Yekaterinburg,
RU
|
|
| 46.250.95.67 |
16.58ms from Yekaterinburg,
RU
|
|
| 92.246.214.225 |
16.24ms from Yekaterinburg,
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 |
|---|---|---|
| 98.90.181.78 |
0.52ms from Ashburn,
US
|
|
| 34.239.130.94 |
0.52ms from Ashburn,
US
|
|
| 12.94.18.238 |
9.68ms from Atlanta,
US
|
|
| 3.3.13.238 |
0.03ms from Bangkok,
TH
|
|
| 54.244.239.190 |
0.19ms from Boardman,
US
|
|
| 41.24.168.94 |
1.63ms from Cape Town,
ZA
|
|
| 125.70.8.254 |
2.13ms from Chengdu,
CN
|
|
| 216.175.17.14 |
3.26ms from Chicago,
US
|
|
| 66.196.1.254 |
3.46ms from Dallas,
US
|
|
| 212.218.20.62 |
1.19ms from Frankfurt am Main,
DE
|
|
| 120.26.46.190 |
2.21ms from Hangzhou,
CN
|
|
| 219.78.76.254 |
0.68ms from Hong Kong,
HK
|
|
| 175.142.89.126 |
1.40ms from Kuala Lumpur,
MY
|
|
| 175.161.186.110 |
8.66ms from Liaoyang,
CN
|
|
| 62.121.17.222 |
4.00ms from London,
GB
|
|
| 88.181.253.30 |
12.22ms from Paris,
FR
|
|
| 39.65.41.62 |
1.49ms from Qingdao,
CN
|
|
| 88.53.247.174 |
1.34ms from Rome,
IT
|
|
| 136.36.4.126 |
2.18ms from Salt Lake City,
US
|
|
| 136.152.230.94 |
2.04ms from San Jose,
US
|
|
| 211.104.208.254 |
7.39ms from Seoul,
KR
|
|
| 121.191.83.62 |
3.20ms from Seoul,
KR
|
|
| 112.187.228.30 |
1.46ms from Seoul,
KR
|
|
| 60.54.194.254 |
1.59ms from Sepang,
MY
|
|
| 97.87.157.46 |
6.44ms from St. Louis,
US
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this ASN. Learn more.
Related Networks
What is an ASN?
Autonomous System Numbers (ASNs) are assigned to entities such as Internet Service Providers and other large organizations that control blocks of IP addresses. This network page, and the organization field that's shown on the main IP address information page and also returned in the geolocation API are based on the ASN.
The ASN details will often correspond to the IP address owner, but for smaller organizations it may be that organization's parent, or their ISP. Find out more about AS41822 at robtex.
Data 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 IPsKeyboard shortcuts
-
/Start search
-
G IGo to My IP page
-
G AGo to My ASN page