Country
—
ASN LANDING PAGE
SYNTSIB-AS - PJSC MegaFon
Last updated · Apr 4, 2026
Country
—
Total prefixes
48
IPv4 prefixes
38
IPv6 prefixes
10
SYNTSIB-AS - PJSC MegaFon currently shows 48 prefixes and 26 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.
SYNTSIB-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.
AS39785
AS39785
—
AS51067
AS51067
—
AS203784
AS203784
—
AS41311
AS41311
—
AS41411
AS41411
—
AS48316
AS48316
—
AS60862
AS60862
—
AS9078
AS9078
—
AS42048
AS42048
—
AS5567
AS5567
—
AS59591
AS59591
—
AS51291
AS51291
—
AS49932
AS49932
—
AS12418
AS12418
—
AS47117
AS47117
—
AS60361
AS60361
—
AS50433
AS50433
—
AS8279
AS8279
—
AS44420
AS44420
—
AS41566
AS41566
—
AS34671
AS34671
—
AS197420
AS197420
—
AS29071
AS29071
—
AS206871
AS206871
—
AS42558
AS42558
—
| Prefix | Name | Country |
|---|---|---|
| 178.176.248.0/24 | AS50928 | — |
| 178.176.249.0/24 | AS50928 | — |
| 178.176.250.0/24 | AS50928 | — |
| 178.176.251.0/24 | AS50928 | — |
| 178.176.252.0/24 | AS50928 | — |
| 178.176.253.0/24 | AS50928 | — |
| 178.23.144.0/21 | AS50928 | — |
| 178.23.148.0/24 | AS50928 | — |
| 178.23.149.0/24 | AS50928 | — |
| 178.23.150.0/24 | AS50928 | — |
| 178.23.151.0/24 | AS50928 | — |
| 188.170.244.0/23 | AS50928 | — |
| 188.170.244.0/24 | AS50928 | — |
| 188.170.245.0/24 | AS50928 | — |
| 188.170.248.0/24 | AS50928 | — |
| 188.170.249.0/24 | AS50928 | — |
| 188.170.250.0/24 | AS50928 | — |
| 188.170.251.0/24 | AS50928 | — |
| 188.170.252.0/24 | AS50928 | — |
| 2a00:9780:100::/40 | AS50928 | — |
| 2a00:9780:200::/40 | AS50928 | — |
| 2a00:9780:300::/40 | AS50928 | — |
| 2a00:9780:400::/40 | AS50928 | — |
| 2a00:9780:500::/40 | AS50928 | — |
| 2a00:9780:600::/40 | AS50928 | — |
| 2a00:9780:700::/40 | AS50928 | — |
| 2a00:9780:800::/40 | AS50928 | — |
| 2a00:9780:900::/40 | AS50928 | — |
| 2a00:9780::/40 | AS50928 | — |
| 31.173.248.0/21 | AS50928 | — |
| 31.173.248.0/24 | AS50928 | — |
| 31.173.249.0/24 | AS50928 | — |
| 31.173.250.0/24 | AS50928 | — |
| 31.173.251.0/24 | AS50928 | — |
| 31.173.252.0/24 | AS50928 | — |
| 31.173.253.0/24 | AS50928 | — |
| 31.173.254.0/24 | AS50928 | — |
| 37.29.80.0/22 | AS50928 | — |
| 37.29.80.0/24 | AS50928 | — |
| 37.29.81.0/24 | AS50928 | — |
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.
AS50928 is an autonomous system number used to identify an independently operated network. The current page associates it with SYNTSIB-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 AS50928. 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 AS50928, 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.