Country
—
ASN LANDING PAGE
edgeconnect-legacy
Last updated · Apr 4, 2026
Country
—
Total prefixes
25
IPv4 prefixes
24
IPv6 prefixes
1
edgeconnect-legacy currently shows 25 prefixes and 47 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.
edgeconnect-legacy 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.
AS37468
AS37468
—
AS37271
AS37271
—
AS6939
AS6939
—
AS5405
AS5405
—
AS34019
AS34019
—
AS20764
AS20764
—
AS35280
AS35280
—
AS50304
AS50304
—
AS34549
AS34549
—
AS1103
AS1103
—
AS3214
AS3214
—
AS41327
AS41327
—
AS58057
AS58057
—
AS25091
AS25091
—
AS50629
AS50629
—
AS56911
AS56911
—
AS3216
AS3216
—
AS8298
AS8298
—
AS33891
AS33891
—
AS34177
AS34177
—
AS39351
AS39351
—
AS41441
AS41441
—
AS29075
AS29075
—
AS34927
AS34927
—
AS58453
AS58453
—
AS24961
AS24961
—
AS4455
AS4455
—
AS37680
AS37680
—
AS328320
AS328320
—
AS917
AS917
—
AS3399
AS3399
—
AS8283
AS8283
—
AS12859
AS12859
—
AS24482
AS24482
—
AS36236
AS36236
—
AS37697
AS37697
—
AS39122
AS39122
—
AS41666
AS41666
—
AS50869
AS50869
—
AS62167
AS62167
—
| Prefix | Name | Country |
|---|---|---|
| 102.176.224.0/20 | AS32437 | — |
| 102.176.224.0/24 | AS32437 | — |
| 102.176.225.0/24 | AS32437 | — |
| 102.176.226.0/24 | AS32437 | — |
| 102.176.227.0/24 | AS32437 | — |
| 102.176.228.0/24 | AS32437 | — |
| 102.176.229.0/24 | AS32437 | — |
| 102.176.230.0/24 | AS32437 | — |
| 102.176.231.0/24 | AS32437 | — |
| 102.176.232.0/24 | AS32437 | — |
| 102.176.233.0/24 | AS32437 | — |
| 102.176.234.0/24 | AS32437 | — |
| 102.176.235.0/24 | AS32437 | — |
| 102.176.236.0/24 | AS32437 | — |
| 102.176.237.0/24 | AS32437 | — |
| 102.176.238.0/24 | AS32437 | — |
| 102.176.239.0/24 | AS32437 | — |
| 160.119.192.0/22 | AS32437 | — |
| 160.119.192.0/24 | AS32437 | — |
| 160.119.193.0/24 | AS32437 | — |
| 160.119.194.0/24 | AS32437 | — |
| 160.119.195.0/24 | AS32437 | — |
| 2c0f:f178::/32 | AS32437 | — |
| 41.223.244.0/22 | AS32437 | — |
| 41.223.244.0/24 | AS32437 | — |
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.
Useful when you want to decide whether this ASN behaves like a CDN, Anycast, or edge-delivery network.
Useful for deciding whether this ASN looks more like website CDN frontage or the real hosting origin.
Useful for tracing the real hosting provider behind an edge or CDN layer.
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.
AS32437 is an autonomous system number used to identify an independently operated network. The current page associates it with edgeconnect-legacy 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 AS32437. 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 AS32437, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Separate public DNS, CDN Anycast, and edge-delivery IP behavior, especially when one IP appears to shift across multiple locations.
Understand how CDN, Anycast, and edge delivery change IP geolocation, latency interpretation, origin tracing, and ASN attribution.
Separate CDN or edge IPs from the real website origin-hosting or server IP behind a domain.
Use DNS, ASN, WHOIS, CNAMEs, HTTP headers, and CDN clues to trace the real hosting or cloud provider behind a website.