Country
—
ASN LANDING PAGE
TELEFONICA CHILE S.A.
Last updated · Apr 4, 2026
Country
—
Total prefixes
41
IPv4 prefixes
35
IPv6 prefixes
6
TELEFONICA CHILE S.A. currently shows 41 prefixes and 52 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.
TELEFONICA CHILE S.A. 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.
AS16629
AS16629
—
AS7418
AS7418
—
AS11340
AS11340
—
AS267717
AS267717
—
AS273019
AS273019
—
AS262237
AS262237
—
AS3360
AS3360
—
AS15311
AS15311
—
AS267728
AS267728
—
AS13424
AS13424
—
AS16990
AS16990
—
AS17147
AS17147
—
AS52226
AS52226
—
AS263807
AS263807
—
AS266726
AS266726
—
AS14795
AS14795
—
AS400696
AS400696
—
AS27880
AS27880
—
AS28099
AS28099
—
AS52353
AS52353
—
AS274073
AS274073
—
AS20015
AS20015
—
AS263816
AS263816
—
AS19351
AS19351
—
AS52396
AS52396
—
AS28082
AS28082
—
AS52441
AS52441
—
AS26610
AS26610
—
AS61483
AS61483
—
AS273237
AS273237
—
AS52460
AS52460
—
AS16874
AS16874
—
AS27678
AS27678
—
AS14259
AS14259
—
AS19338
AS19338
—
AS52411
AS52411
—
AS136907
AS136907
—
AS269993
AS269993
—
AS20144
AS20144
—
AS271871
AS271871
—
| Prefix | Name | Country |
|---|---|---|
| 164.77.27.0/24 | AS7004 | — |
| 186.103.155.0/24 | AS7004 | — |
| 186.103.156.0/23 | AS7004 | — |
| 186.103.158.0/23 | AS7004 | — |
| 186.103.240.0/20 | AS7004 | — |
| 186.148.0.0/18 | AS7004 | — |
| 186.148.34.0/24 | AS7004 | — |
| 186.148.38.0/24 | AS7004 | — |
| 186.148.40.0/24 | AS7004 | — |
| 186.148.41.0/24 | AS7004 | — |
| 186.148.7.0/24 | AS7004 | — |
| 190.82.114.0/23 | AS7004 | — |
| 200.10.224.0/24 | AS7004 | — |
| 200.113.166.0/24 | AS7004 | — |
| 200.12.18.0/24 | AS7004 | — |
| 200.12.23.0/24 | AS7004 | — |
| 200.12.25.0/24 | AS7004 | — |
| 200.12.26.0/24 | AS7004 | — |
| 200.28.14.0/24 | AS7004 | — |
| 200.29.34.0/24 | AS7004 | — |
| 200.29.42.0/24 | AS7004 | — |
| 200.50.42.0/24 | AS7004 | — |
| 200.54.109.0/24 | AS7004 | — |
| 200.54.110.0/24 | AS7004 | — |
| 200.91.0.0/19 | AS7004 | — |
| 200.91.0.0/24 | AS7004 | — |
| 200.91.12.0/24 | AS7004 | — |
| 200.91.13.0/24 | AS7004 | — |
| 200.91.15.0/24 | AS7004 | — |
| 200.91.2.0/24 | AS7004 | — |
| 200.91.21.0/24 | AS7004 | — |
| 200.91.27.0/24 | AS7004 | — |
| 200.91.31.0/24 | AS7004 | — |
| 200.91.8.0/24 | AS7004 | — |
| 2800:4d0::/32 | AS7004 | — |
| 2800:550:4::/48 | AS7004 | — |
| 2800:550::/32 | AS7004 | — |
| 2800:550:ae::/48 | AS7004 | — |
| 2800:550:fe::/48 | AS7004 | — |
| 2800:550:ff::/48 | AS7004 | — |
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.
AS7004 is an autonomous system number used to identify an independently operated network. The current page associates it with TELEFONICA CHILE S.A. 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 AS7004. 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 AS7004, 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.