Country
—
ASN LANDING PAGE
SONICDUO-AS PJSC MegaFon
Last updated · Jul 20, 2026
Country
—
Total prefixes
88
IPv4 prefixes
69
IPv6 prefixes
19
SONICDUO-AS PJSC MegaFon currently reports 88 prefixes and 41 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.
SONICDUO-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.
AS25189
AS25189
—
AS210239
AS210239
—
AS24866
AS24866
—
AS8263
AS8263
—
AS212211
AS212211
—
AS207984
AS207984
—
AS208447
AS208447
—
AS201788
AS201788
—
AS30853
AS30853
—
AS51339
AS51339
—
AS51680
AS51680
—
AS57645
AS57645
—
AS58094
AS58094
—
AS60065
AS60065
—
AS201914
AS201914
—
AS47783
AS47783
—
AS41388
AS41388
—
AS211076
AS211076
—
AS206424
AS206424
—
AS39850
AS39850
—
AS64450
AS64450
—
AS39154
AS39154
—
AS216236
AS216236
—
AS215809
AS215809
—
AS198481
AS198481
—
AS205349
AS205349
—
AS56996
AS56996
—
AS39678
AS39678
—
AS47358
AS47358
—
AS41029
AS41029
—
AS8441
AS8441
—
AS8742
AS8742
—
AS51288
AS51288
—
AS57107
AS57107
—
AS49450
AS49450
—
AS203699
AS203699
—
AS198806
AS198806
—
AS202202
AS202202
—
AS60864
AS60864
—
AS48891
AS48891
—
| Prefix | Name | Country |
|---|---|---|
| 109.188.112.0/23 | AS25159 | — |
| 109.188.114.0/24 | AS25159 | — |
| 109.188.124.0/24 | AS25159 | — |
| 109.188.125.0/24 | AS25159 | — |
| 109.188.64.0/19 | AS25159 | — |
| 109.188.96.0/21 | AS25159 | — |
| 128.204.76.0/22 | AS25159 | — |
| 128.204.76.0/23 | AS25159 | — |
| 128.204.78.0/23 | AS25159 | — |
| 130.49.216.0/24 | AS25159 | — |
| 178.176.0.0/19 | AS25159 | — |
| 178.176.32.0/21 | AS25159 | — |
| 178.176.40.0/21 | AS25159 | — |
| 178.176.52.0/22 | AS25159 | — |
| 178.176.72.0/21 | AS25159 | — |
| 178.176.92.0/22 | AS25159 | — |
| 178.177.0.0/18 | AS25159 | — |
| 178.178.192.0/22 | AS25159 | — |
| 178.178.198.0/23 | AS25159 | — |
| 178.178.216.0/21 | AS25159 | — |
| 178.178.235.0/24 | AS25159 | — |
| 178.178.236.0/24 | AS25159 | — |
| 188.170.0.0/19 | AS25159 | — |
| 188.170.32.0/21 | AS25159 | — |
| 188.170.40.0/21 | AS25159 | — |
| 193.201.228.0/22 | AS25159 | — |
| 195.16.110.0/23 | AS25159 | — |
| 195.16.96.0/19 | AS25159 | — |
| 195.230.70.0/23 | AS25159 | — |
| 195.230.91.0/24 | AS25159 | — |
| 195.230.92.0/24 | AS25159 | — |
| 212.69.106.0/24 | AS25159 | — |
| 212.69.113.0/24 | AS25159 | — |
| 212.69.114.0/24 | AS25159 | — |
| 212.69.125.0/24 | AS25159 | — |
| 212.69.96.0/19 | AS25159 | — |
| 213.243.109.0/24 | AS25159 | — |
| 213.243.116.0/24 | AS25159 | — |
| 2a03:d000:4000::/36 | AS25159 | — |
| 2a03:d000:4100::/40 | AS25159 | — |
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.
AS25159 is an autonomous system number. The current source associates it with SONICDUO-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 AS25159. 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 AS25159, 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.