Country
—
ASN LANDING PAGE
ENETWORKS
Last updated · Apr 4, 2026
Country
—
Total prefixes
18
IPv4 prefixes
13
IPv6 prefixes
5
ENETWORKS currently shows 18 prefixes and 49 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.
ENETWORKS 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.
AS3741
AS3741
—
AS30844
AS30844
—
AS6939
AS6939
—
AS37468
AS37468
—
AS23764
AS23764
—
AS37662
AS37662
—
AS37271
AS37271
—
AS6774
AS6774
—
AS36874
AS36874
—
AS33763
AS33763
—
AS37613
AS37613
—
AS36994
AS36994
—
AS37035
AS37035
—
AS20473
AS20473
—
AS16637
AS16637
—
AS58453
AS58453
—
AS16509
AS16509
—
AS60171
AS60171
—
AS327708
AS327708
—
AS37273
AS37273
—
AS39120
AS39120
—
AS36236
AS36236
—
AS60068
AS60068
—
AS327782
AS327782
—
AS37678
AS37678
—
AS327693
AS327693
—
AS37697
AS37697
—
AS37153
AS37153
—
AS37239
AS37239
—
AS37236
AS37236
—
AS36944
AS36944
—
AS2018
AS2018
—
AS37179
AS37179
—
AS37497
AS37497
—
AS4134
AS4134
—
AS19711
AS19711
—
AS20459
AS20459
—
AS33765
AS33765
—
AS37119
AS37119
—
AS328748
AS328748
—
| Prefix | Name | Country |
|---|---|---|
| 154.72.104.0/22 | AS32653 | — |
| 154.72.96.0/20 | AS32653 | — |
| 154.72.96.0/21 | AS32653 | — |
| 2c0f:fbf0:1::/48 | AS32653 | — |
| 2c0f:fbf0::/28 | AS32653 | — |
| 2c0f:fbf0::/48 | AS32653 | — |
| 2c0f:fbf4:8000::/48 | AS32653 | — |
| 2c0f:fbf8:300::/48 | AS32653 | — |
| 41.222.48.0/21 | AS32653 | — |
| 41.77.152.0/21 | AS32653 | — |
| 41.77.152.0/22 | AS32653 | — |
| 41.77.156.0/23 | AS32653 | — |
| 41.77.158.0/23 | AS32653 | — |
| 45.220.128.0/17 | AS32653 | — |
| 45.220.128.0/19 | AS32653 | — |
| 45.220.160.0/20 | AS32653 | — |
| 45.220.176.0/20 | AS32653 | — |
| 45.220.192.0/18 | AS32653 | — |
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.
AS32653 is an autonomous system number used to identify an independently operated network. The current page associates it with ENETWORKS 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 AS32653. 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 AS32653, 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.