94.25.184.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 | 94.25.128.0/17 |
| Registry | RIPE |
| ID | MF-MOSCOW-MBB-YOTA-94-25-184 |
WHOIS Details
inetnum: 94.25.186.0 - 94.25.191.255 netname: MF-MOSCOW-MBB-YOTA-94-25-184 country: RU admin-c: MA23317-RIPE tech-c: MWST-RIPE status: ASSIGNED PA mnt-by: GDC-TR-CoreIP created: 2025-04-18T04:23:48Z last-modified: 2025-04-18T04:23:48Z 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 role: MegaFon PJSC - GNOC West TRM IP address: PJSC MegaFon address: 41, Oruzheyniy lane address: Moscow, 127006 e-mail: info@megafon.ru e-mail: gnocwest_tr@megafon.ru notify: lir@megafon.ru abuse-mailbox: abuse-mailbox@megafon.ru remarks: ----------------------------------------------------------- remarks: Customer Service Center, is available at 24 x 7 remarks: ----------------------------------------------------------- remarks: Technical questions: gnocwest_tr@megafon.ru remarks: Routing and peering: gnoceast_backbone@megafon.ru remarks: ----------------------------------------------------------- remarks: SPAM and Network security: abuse-mailbox@megafon.ru remarks: Please use abuse-mailbox@megafon.ru e-mail address for complaints. remarks: All messages to any other our address, relative to SPAM remarks: or security issues, will not be concerned. remarks: ----------------------------------------------------------- remarks: Information: http://www.megafon.ru remarks: ----------------------------------------------------------- admin-c: GMV-RIPE nic-hdl: MWST-RIPE mnt-by: MEGAFON-RIPE-MNT mnt-by: MEGAFON-WEST-MNT created: 2015-02-17T12:00:24Z last-modified: 2023-02-04T07:47:33Z source: RIPE route: 94.25.184.0/21 descr: MF-MOSCOW-MBB-YOTA-94-25-184 origin: AS25159 mnt-by: MEGAFON-AUTO-MNT mnt-by: GDC-TR-CoreIP created: 2016-11-03T08:07:17Z last-modified: 2022-08-23T08:16:05Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 94.25.184.0/21
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 94.25.128.0/17 | AS25159 | PJSC MegaFon | 32,768 |
| 94.25.128.0/17 | AS31133 | PJSC MegaFon | 32,768 |
| 94.25.128.0/17 | AS47395 | PJSC MegaFon | 32,768 |
Nearby Ranges
BGP prefixes that overlap with 94.25.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 94.25.0.0/17 | AS12389 | PJSC Rostelecom | 32,768 |
| 94.25.128.0/17 | AS25159 | PJSC MegaFon | 32,768 |
| 94.25.128.0/17 | AS31133 | PJSC MegaFon | 32,768 |
| 94.25.128.0/17 | AS47395 | PJSC MegaFon | 32,768 |
| 94.25.144.0/20 | AS25159 | PJSC MegaFon | 4,096 |
| 94.25.216.0/21 | AS31213 | infrastructure in SPb | 2,048 |
| 94.25.224.0/21 | AS31213 | PJSC MegaFon | 2,048 |
| 94.25.248.0/21 | AS20632 | infrastructure in SPb | 2,048 |
| 94.25.172.0/22 | AS25159 | PJSC MegaFon | 1,024 |
| 94.25.208.0/22 | AS31213 | infrastructure in Saint-Petersburg | 1,024 |
| 94.25.168.0/22 | AS25159 | PJSC MegaFon | 1,024 |
| 94.25.30.0/24 | AS209313 | JSC Rostelecom client (city Slantsy) 08-12482 | 256 |
| 94.25.160.0/24 | AS25159 | YOTA - Tulskaya obl. | 256 |
| 94.25.164.0/24 | AS25159 | YOTA - Ryazanskaya obl. | 256 |
Hosted domains
There is 1 domain name hosted across 1 IP address on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|---|---|
| 94.25.187.86 | szpower.org | 1 |
Hosted domains API
Pingable IPs
No IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
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 |
|---|---|---|
| 204.0.241.69 |
0.75ms from Ashburn,
US
|
|
| 210.73.56.5 |
2.79ms from Beijing,
CN
|
|
| 12.191.38.133 |
5.34ms from Columbus,
US
|
|
| 96.66.22.85 |
8.33ms from Detroit,
US
|
|
| 121.199.35.69 |
5.58ms from Hangzhou,
CN
|
|
| 115.98.83.213 |
1.42ms from Hyderabad,
IN
|
|
| 3.10.221.245 |
0.18ms from London,
GB
|
|
| 75.74.128.197 |
2.91ms from Miami,
US
|
|
| 13.203.24.69 |
0.30ms from Mumbai,
IN
|
|
| 112.235.213.149 |
7.04ms from Qingdao,
CN
|
|
| 222.116.37.229 |
10.04ms from Seoul,
KR
|
|
| 71.15.72.21 |
1.88ms from St. Louis,
US
|
|
| 61.230.79.149 |
0.87ms from Taipei,
TW
|
|
| 171.125.148.5 |
6.83ms from Taiyuan,
CN
|
|
| 183.203.232.101 |
7.47ms from Taiyuan,
CN
|
|
| 221.170.31.37 |
4.42ms from Tokyo,
JP
|
|
| 97.80.199.53 |
16.67ms from Atlanta,
US
|
|
| 120.6.135.133 |
10.40ms from Beijing,
CN
|
|
| 44.244.138.213 |
0.49ms from Boardman,
US
|
|
| 210.84.52.133 |
1.89ms from Brisbane,
AU
|
|
| 223.185.80.21 |
6.61ms from Chennai,
IN
|
|
| 172.244.7.101 |
1.44ms from Chicago,
US
|
|
| 68.43.98.5 |
8.74ms from Flint,
US
|
|
| 34.103.227.165 |
0.92ms from Frankfurt am Main,
DE
|
|
| 5.253.145.21 |
0.70ms from Krasnoyarsk,
RU
|
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