188.170.32.0/21
AS25159 · PJSC MegaFon
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 | megafon.ru |
| ASN | AS25159 |
| Parent Range | 188.170.0.0/16 |
| Registry | RIPE |
| ID | MF-MOSCOW-MBB-POOL-188-170-32 |
WHOIS Details
inetnum: 188.170.32.0 - 188.170.39.255 netname: MF-MOSCOW-MBB-POOL-188-170-32 descr: Megafon-Moscow Broadband clients descr: Moscow Branch of OJSC MegaFon country: RU status: ASSIGNED PA admin-c: MA23317-RIPE tech-c: MA23317-RIPE mnt-routes: GDC-TR-CoreIP mnt-lower: GDC-TR-CoreIP mnt-lower: MEGAFON-AUTO-MNT mnt-by: MEGAFON-AUTO-MNT mnt-by: MEGAFON-RIPE-MNT mnt-by: GDC-TR-CoreIP created: 2016-10-28T11:40:11Z mnt-domains: MEGAFON-DNS-MNT last-modified: 2023-06-29T07:45:53Z source: RIPE abuse-email: abuse-mailbox@megafon.ru abuse-c: MFON-RIPE abuse-org: ORG-OM1-RIPE role: Mobile address: Samara e-mail: GDC-TR-CoreIP@megafon.ru nic-hdl: MA23317-RIPE mnt-by: GDC-TR-CoreIP created: 2020-02-05T11:44:29Z last-modified: 2020-02-05T11:44:29Z source: RIPE route: 188.170.32.0/21 descr: MF-MOSCOW-MBB-FIXEDIP-188-170-32-0 origin: AS25159 mnt-by: MEGAFON-AUTO-MNT mnt-by: GDC-TR-CoreIP created: 2016-11-01T13:52:54Z last-modified: 2021-08-13T13:33:04Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 188.170.32.0/21
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 188.170.0.0/16 | AS31133 | PJSC MegaFon | 65,536 |
Nearby Ranges
BGP prefixes that overlap with 188.170.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 188.170.0.0/16 | AS31133 | PJSC MegaFon | 65,536 |
| 188.170.168.0/21 | AS31163 | Mobile Subscribers | 2,048 |
| 188.170.40.0/21 | AS25159 | Megafon-Moscow Mobile Broadband clients | 2,048 |
| 188.170.72.0/21 | AS31213 | PJSC MegaFon | 2,048 |
| 188.170.240.0/22 | AS31205 | PJSC MegaFon | 1,024 |
| 188.170.228.0/23 | AS31195 | East Branch of PJSC MegaFon - Irkutsk Broadband | 512 |
| 188.170.244.0/23 | AS50928 | Siberian Branch of OJSC Megafon | 512 |
| 188.170.104.0/24 | AS29648 | Ural Branch of OJSC MegaFon Ekaterinburg | 256 |
| 188.170.121.0/24 | AS29648 | Ural Branch of OJSC MegaFon Kirov | 256 |
| 188.170.109.0/24 | AS29648 | Ural Branch of OJSC MegaFon Tumen | 256 |
| 188.170.110.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.111.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.112.0/24 | AS29648 | Ural Branch of OJSC MegaFon Tumen | 256 |
| 188.170.103.0/24 | AS29648 | Ural Branch of OJSC MegaFon Izhevsk | 256 |
| 188.170.108.0/24 | AS29648 | Ural Branch of OJSC MegaFon Noyabrsk | 256 |
| 188.170.117.0/24 | AS29648 | Ural Branch of OJSC MegaFon Syktyvkar | 256 |
| 188.170.107.0/24 | AS29648 | Ural Branch of OJSC MegaFon Noyabrsk | 256 |
| 188.170.102.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.118.0/24 | AS29648 | Ural Branch of OJSC MegaFon Surgut | 256 |
| 188.170.119.0/24 | AS29648 | Ural Branch of OJSC MegaFon Perm | 256 |
| 188.170.120.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.144.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.122.0/24 | AS29648 | Ural Branch of OJSC MegaFon Izhevsk | 256 |
| 188.170.123.0/24 | AS29648 | Ural Branch of OJSC MegaFon Ekaterinburg | 256 |
| 188.170.124.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.125.0/24 | AS29648 | Ural Branch of OJSC MegaFon Yekaterinburg | 256 |
| 188.170.126.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.127.0/24 | AS29648 | Ural Branch of OJSC MegaFon Kirov | 256 |
| 188.170.97.0/24 | AS29648 | Ural Branch of OJSC MegaFon Chelyabinsk | 256 |
| 188.170.116.0/24 | AS29648 | Ural Branch of OJSC MegaFon Ekaterinburg | 256 |
| 188.170.129.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.115.0/24 | AS29648 | Ural Branch of OJSC MegaFon Noyabrsk | 256 |
| 188.170.106.0/24 | AS29648 | Ural Branch of OJSC MegaFon Kirov | 256 |
| 188.170.128.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.130.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.131.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.132.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.133.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.134.0/24 | AS31133 | Fix-Cust AtomData | 256 |
| 188.170.136.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.137.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.139.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.140.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.141.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.142.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.114.0/24 | AS29648 | Ural Branch of OJSC MegaFon Surgut | 256 |
| 188.170.145.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.146.0/24 | AS31133 | PJSC MegaFon | 256 |
| 188.170.99.0/24 | AS29648 | Ural Branch of OJSC MegaFon Surgut | 256 |
Hosted domains
There are 3 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 |
|---|
Hosted domains API
Pingable IPs
502 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 188.170.38.126 |
12.86ms from Moscow,
RU
|
|
| 188.170.35.44 |
13.08ms from Moscow,
RU
|
|
| 188.170.33.67 |
15.27ms from Moscow,
RU
|
|
| 188.170.39.251 |
13.37ms from Moscow,
RU
|
|
| 188.170.37.118 |
14.96ms from Moscow,
RU
|
|
| 188.170.34.168 |
15.64ms from Moscow,
RU
|
|
| 188.170.36.151 |
12.93ms from Moscow,
RU
|
|
| 188.170.32.198 |
12.80ms from Moscow,
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 |
|---|---|---|
| 34.45.122.245 |
0.11ms from Council Bluffs,
US
|
|
| 34.134.151.117 |
0.11ms from Council Bluffs,
US
|
|
| 218.92.91.245 |
7.96ms from Huai'an,
CN
|
|
| 78.173.255.85 |
5.24ms from Istanbul,
TR
|
|
| 83.132.141.165 |
13.83ms from Lisbon,
PT
|
|
| 66.195.78.197 |
0.74ms from New York City,
US
|
|
| 205.234.161.21 |
0.14ms from Piscataway,
US
|
|
| 200.38.243.165 |
19.56ms from Santiago de Querétaro,
MX
|
|
| 177.76.148.85 |
4.46ms from Sao Paulo,
BR
|
|
| 120.25.162.149 |
1.52ms from Shenzhen,
CN
|
|
| 13.115.99.149 |
0.16ms from Tokyo,
JP
|
|
| 126.15.53.117 |
3.07ms from Tokyo,
JP
|
|
| 90.173.151.117 |
6.37ms from Zaragoza,
ES
|
|
| 37.76.71.37 |
4.99ms from Budapest,
HU
|
|
| 68.112.215.181 |
16.03ms from Dallas,
US
|
|
| 68.11.173.69 |
13.47ms from Dallas,
US
|
|
| 51.112.30.213 |
0.11ms from Dubai,
AE
|
|
| 79.125.93.69 |
0.25ms from Dublin,
IE
|
|
| 183.151.232.85 |
7.65ms from Hangzhou,
CN
|
|
| 41.1.95.229 |
4.15ms from Johannesburg,
ZA
|
|
| 86.138.44.133 |
9.03ms from London,
GB
|
|
| 213.105.186.37 |
1.51ms from London,
GB
|
|
| 72.193.148.53 |
6.61ms from Los Angeles,
US
|
|
| 46.24.160.181 |
10.03ms from Madrid,
ES
|
|
| 98.244.187.117 |
14.95ms from Orlando,
US
|
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