Country
—
ASN LANDING PAGE
ESPANIX-RS-AS - ASOCIACION ESPANIX
Last updated · Apr 4, 2026
Country
—
Total prefixes
3
IPv4 prefixes
2
IPv6 prefixes
1
ESPANIX-RS-AS - ASOCIACION ESPANIX currently shows 3 prefixes and 43 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.
ESPANIX-RS-AS - ASOCIACION ESPANIX 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.
AS12430
AS12430
—
AS8903
AS8903
—
AS208591
AS208591
—
AS29119
AS29119
—
AS200845
AS200845
—
AS201746
AS201746
—
AS202513
AS202513
—
AS208569
AS208569
—
AS2686
AS2686
—
AS57286
AS57286
—
AS60171
AS60171
—
AS202844
AS202844
—
AS210350
AS210350
—
AS211074
AS211074
—
AS13150
AS13150
—
AS35699
AS35699
—
AS57976
AS57976
—
AS197927
AS197927
—
AS205718
AS205718
—
AS212087
AS212087
—
AS6939
AS6939
—
AS23764
AS23764
—
AS3303
AS3303
—
AS33891
AS33891
—
AS22356
AS22356
—
AS8218
AS8218
—
AS7713
AS7713
—
AS207336
AS207336
—
AS4455
AS4455
—
AS14840
AS14840
—
AS6424
AS6424
—
AS9498
AS9498
—
AS15830
AS15830
—
AS29049
AS29049
—
AS29680
AS29680
—
AS37721
AS37721
—
AS39120
AS39120
—
AS49544
AS49544
—
AS51185
AS51185
—
AS60171
AS60171
—
AS198150
AS198150
—
AS212483
AS212483
—
AS263444
AS263444
—
| Prefix | Name | Country |
|---|---|---|
| 185.79.172.0/23 | AS6895 | — |
| 185.79.174.0/24 | AS6895 | — |
| 2001:7f8:f::/48 | AS6895 | — |
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 Oracle Cloud / OCI enterprise cloud infrastructure or another generic hosting network.
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.
AS6895 is an autonomous system number used to identify an independently operated network. The current page associates it with ESPANIX-RS-AS - ASOCIACION ESPANIX 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 AS6895. 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 AS6895, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Use ASN, WHOIS, prefixes, and cloud-network context to decide whether an IP looks more like Oracle Cloud or OCI 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.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.