Country
—
ASN LANDING PAGE
SYNTSIB-AS PJSC MegaFon
Last updated · Jul 20, 2026
Country
—
Total prefixes
47
IPv4 prefixes
37
IPv6 prefixes
10
SYNTSIB-AS PJSC MegaFon currently reports 47 prefixes and 26 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
SYNTSIB-AS PJSC MegaFon is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS39785
AS39785
—
AS51067
AS51067
—
AS203784
AS203784
—
AS48316
AS48316
—
AS42048
AS42048
—
AS8279
AS8279
—
AS41311
AS41311
—
AS41411
AS41411
—
AS60862
AS60862
—
AS59591
AS59591
—
AS9078
AS9078
—
AS29071
AS29071
—
AS5567
AS5567
—
AS49932
AS49932
—
AS12418
AS12418
—
AS51291
AS51291
—
AS47117
AS47117
—
AS44420
AS44420
—
AS50433
AS50433
—
AS41566
AS41566
—
AS197420
AS197420
—
AS34671
AS34671
—
AS197482
AS197482
—
AS206871
AS206871
—
AS214395
AS214395
—
| 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 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS50928 is an autonomous system number. The current source associates it with SYNTSIB-AS PJSC MegaFon and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
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.
Open a concrete IP page to check how the address maps into AS50928, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.