Country
—
ASN LANDING PAGE
AMAZON-LEO - Amazon Technologies Inc.
Last updated · Apr 4, 2026
Country
—
Total prefixes
50
IPv4 prefixes
37
IPv6 prefixes
13
AMAZON-LEO - Amazon Technologies Inc. currently shows 50 prefixes and 2 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.
AMAZON-LEO - Amazon Technologies Inc. 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.
Detailed data for this ASN is not available right now.
| Prefix | Name | Country |
|---|---|---|
| 2606:7b40:1b13::/48 | AS801 | — |
| 2606:7b40:1b16::/48 | AS801 | — |
| 2631:0:1000::/40 | AS801 | — |
| 2631:0:1100::/40 | AS801 | — |
| 2631:0:1400::/40 | AS801 | — |
| 2631:0:1500::/40 | AS801 | — |
| 2631:0:1800::/48 | AS801 | — |
| 2631:0:1::/48 | AS801 | — |
| 2631:0:200::/40 | AS801 | — |
| 2631:0:2::/48 | AS801 | — |
| 2631:0:300::/40 | AS801 | — |
| 2631:0:4::/48 | AS801 | — |
| 2631:0:a::/48 | AS801 | — |
| 35.96.24.0/23 | AS801 | — |
| 35.96.244.0/24 | AS801 | — |
| 35.96.26.0/23 | AS801 | — |
| 35.96.32.0/24 | AS801 | — |
| 35.96.33.0/24 | AS801 | — |
| 35.96.34.0/24 | AS801 | — |
| 35.96.35.0/24 | AS801 | — |
| 35.96.36.0/24 | AS801 | — |
| 35.96.38.0/24 | AS801 | — |
| 35.96.39.0/24 | AS801 | — |
| 35.96.40.0/24 | AS801 | — |
| 35.96.43.0/24 | AS801 | — |
| 35.96.44.0/24 | AS801 | — |
| 35.96.45.0/24 | AS801 | — |
| 35.96.46.0/24 | AS801 | — |
| 35.96.47.0/24 | AS801 | — |
| 35.96.48.0/23 | AS801 | — |
| 35.96.5.0/24 | AS801 | — |
| 35.96.50.0/23 | AS801 | — |
| 35.96.52.0/23 | AS801 | — |
| 35.96.54.0/23 | AS801 | — |
| 35.96.56.0/24 | AS801 | — |
| 35.96.58.0/23 | AS801 | — |
| 35.96.60.0/23 | AS801 | — |
| 35.97.129.0/24 | AS801 | — |
| 35.97.130.0/24 | AS801 | — |
| 35.97.144.0/21 | AS801 | — |
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 for deciding whether this ASN behaves more like AWS cloud infrastructure, a regional Amazon network, or another hosted platform.
Continue from this ASN into cloud-provider, hosting, and VPS ownership analysis.
Useful for deciding whether this ASN looks more like cloud infrastructure or traditional website hosting.
Useful for placing this ASN into datacenter-versus-residential attribution analysis.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
AS801 is an autonomous system number used to identify an independently operated network. The current page associates it with AMAZON-LEO - Amazon Technologies Inc. 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 AS801. 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 AS801, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Use ASN, WHOIS, prefixes, and cloud-platform context to decide whether an IP looks more like AWS or broader Amazon infrastructure.
Determine whether an IP belongs to AWS, Google Cloud, Azure, or another cloud network by combining ASN, WHOIS, prefixes, and organization data.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.
Separate cloud-server IPs, traditional web-hosting IPs, shared-hosting IPs, and website-hosting networks through ASN, WHOIS, organization, and deployment signals.