Country
—
ASN LANDING PAGE
PETERSTAR-AS PJSC MegaFon
Last updated · Jul 20, 2026
Country
—
Total prefixes
66
IPv4 prefixes
63
IPv6 prefixes
3
PETERSTAR-AS PJSC MegaFon currently reports 66 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.
PETERSTAR-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.
AS41864
AS41864
—
AS200123
AS200123
—
AS42340
AS42340
—
AS44665
AS44665
—
AS57451
AS57451
—
AS57573
AS57573
—
AS198626
AS198626
—
AS201913
AS201913
—
AS211637
AS211637
—
AS51723
AS51723
—
AS8662
AS8662
—
AS58084
AS58084
—
AS48853
AS48853
—
AS206536
AS206536
—
AS33908
AS33908
—
AS50105
AS50105
—
AS60623
AS60623
—
AS198074
AS198074
—
AS44662
AS44662
—
AS50571
AS50571
—
AS201016
AS201016
—
AS51998
AS51998
—
AS209096
AS209096
—
AS204531
AS204531
—
AS200496
AS200496
—
AS205060
AS205060
—
AS62402
AS62402
—
AS49994
AS49994
—
AS31503
AS31503
—
AS62056
AS62056
—
AS50222
AS50222
—
AS201511
AS201511
—
AS29038
AS29038
—
AS207438
AS207438
—
AS44263
AS44263
—
AS199658
AS199658
—
AS29114
AS29114
—
AS199112
AS199112
—
AS207665
AS207665
—
AS47763
AS47763
—
| Prefix | Name | Country |
|---|---|---|
| 109.124.108.0/22 | AS20632 | — |
| 109.124.64.0/18 | AS20632 | — |
| 109.74.112.0/20 | AS20632 | — |
| 176.192.126.0/24 | AS20632 | — |
| 176.192.127.0/24 | AS20632 | — |
| 195.131.14.0/24 | AS20632 | — |
| 195.131.38.0/24 | AS20632 | — |
| 195.144.224.0/19 | AS20632 | — |
| 195.5.128.0/19 | AS20632 | — |
| 212.119.160.0/19 | AS20632 | — |
| 212.14.160.0/19 | AS20632 | — |
| 212.44.64.0/19 | AS20632 | — |
| 212.48.155.0/24 | AS20632 | — |
| 213.154.160.0/21 | AS20632 | — |
| 213.154.168.0/21 | AS20632 | — |
| 213.154.176.0/21 | AS20632 | — |
| 213.154.184.0/21 | AS20632 | — |
| 213.168.32.0/19 | AS20632 | — |
| 213.172.0.0/19 | AS20632 | — |
| 213.182.160.0/19 | AS20632 | — |
| 217.195.64.0/19 | AS20632 | — |
| 2a03:d000:9008::/46 | AS20632 | — |
| 2a03:d000:9008::/48 | AS20632 | — |
| 2a03:d000:9009::/48 | AS20632 | — |
| 46.47.192.0/18 | AS20632 | — |
| 46.47.202.0/24 | AS20632 | — |
| 62.16.101.0/24 | AS20632 | — |
| 62.16.102.0/24 | AS20632 | — |
| 62.16.103.0/24 | AS20632 | — |
| 62.16.104.0/24 | AS20632 | — |
| 62.16.105.0/24 | AS20632 | — |
| 62.16.106.0/24 | AS20632 | — |
| 62.16.107.0/24 | AS20632 | — |
| 62.16.108.0/24 | AS20632 | — |
| 62.16.109.0/24 | AS20632 | — |
| 62.16.112.0/24 | AS20632 | — |
| 62.16.117.0/24 | AS20632 | — |
| 62.16.119.0/24 | AS20632 | — |
| 62.16.99.0/24 | AS20632 | — |
| 62.182.128.0/21 | AS20632 | — |
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.
AS20632 is an autonomous system number. The current source associates it with PETERSTAR-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 AS20632. 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 AS20632, 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.