Country
—
ASN LANDING PAGE
GARS-AS - PJSC MegaFon
Last updated · Apr 4, 2026
Country
—
Total prefixes
36
IPv4 prefixes
35
IPv6 prefixes
1
GARS-AS - PJSC MegaFon currently shows 36 prefixes and 42 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
GARS-AS - PJSC MegaFon is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS202344
AS202344
—
AS48197
AS48197
—
AS198700
AS198700
—
AS47470
AS47470
—
AS59916
AS59916
—
AS34121
AS34121
—
AS212764
AS212764
—
AS60186
AS60186
—
AS43907
AS43907
—
AS41774
AS41774
—
AS59530
AS59530
—
AS206850
AS206850
—
AS44900
AS44900
—
AS204574
AS204574
—
AS39678
AS39678
—
AS47819
AS47819
—
AS213133
AS213133
—
AS198770
AS198770
—
AS209701
AS209701
—
AS58084
AS58084
—
AS35774
AS35774
—
AS216214
AS216214
—
AS60826
AS60826
—
AS200622
AS200622
—
AS209773
AS209773
—
AS51472
AS51472
—
AS200048
AS200048
—
AS50024
AS50024
—
AS197379
AS197379
—
AS200166
AS200166
—
AS198821
AS198821
—
AS211076
AS211076
—
AS211247
AS211247
—
AS56829
AS56829
—
AS201018
AS201018
—
AS204827
AS204827
—
AS60388
AS60388
—
AS35119
AS35119
—
AS200152
AS200152
—
AS202156
AS202156
—
| Prefix | Name | Country |
|---|---|---|
| 109.73.0.0/22 | AS31261 | — |
| 109.73.12.0/23 | AS31261 | — |
| 109.73.4.0/22 | AS31261 | — |
| 109.73.8.0/22 | AS31261 | — |
| 185.196.246.0/23 | AS31261 | — |
| 185.22.24.0/24 | AS31261 | — |
| 185.6.172.0/22 | AS31261 | — |
| 185.6.174.0/24 | AS31261 | — |
| 185.68.145.0/24 | AS31261 | — |
| 185.68.146.0/23 | AS31261 | — |
| 188.164.209.0/24 | AS31261 | — |
| 188.164.212.0/24 | AS31261 | — |
| 188.164.214.0/23 | AS31261 | — |
| 188.68.189.0/24 | AS31261 | — |
| 217.171.152.0/21 | AS31261 | — |
| 2a02:330::/45 | AS31261 | — |
| 37.16.80.0/22 | AS31261 | — |
| 5.8.177.0/24 | AS31261 | — |
| 77.220.209.0/24 | AS31261 | — |
| 77.220.211.0/24 | AS31261 | — |
| 77.242.15.0/24 | AS31261 | — |
| 77.74.72.0/22 | AS31261 | — |
| 77.74.77.0/24 | AS31261 | — |
| 77.74.78.0/24 | AS31261 | — |
| 77.74.79.0/24 | AS31261 | — |
| 81.23.0.0/21 | AS31261 | — |
| 81.23.14.0/24 | AS31261 | — |
| 81.23.8.0/23 | AS31261 | — |
| 81.23.9.0/24 | AS31261 | — |
| 83.220.32.0/19 | AS31261 | — |
| 89.107.141.0/24 | AS31261 | — |
| 89.107.142.0/23 | AS31261 | — |
| 91.217.227.0/24 | AS31261 | — |
| 93.191.16.0/21 | AS31261 | — |
| 93.191.23.0/24 | AS31261 | — |
| 94.124.192.0/21 | AS31261 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS31261 is an autonomous system number used to identify an independently operated network. The current page associates it with GARS-AS - PJSC MegaFon in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS31261. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS31261, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.