Country
—
ASN LANDING PAGE
Telefonica de Argentina
Last updated · Apr 4, 2026
Country
—
Total prefixes
226
IPv4 prefixes
205
IPv6 prefixes
21
Telefonica de Argentina currently shows 226 prefixes and 44 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 de Argentina 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.
AS7303
AS7303
—
AS16814
AS16814
—
AS52361
AS52361
—
AS264758
AS264758
—
AS265798
AS265798
—
AS263693
AS263693
—
AS264685
AS264685
—
AS272925
AS272925
—
AS52327
AS52327
—
AS28075
AS28075
—
AS52465
AS52465
—
AS270089
AS270089
—
AS28073
AS28073
—
AS20207
AS20207
—
AS266806
AS266806
—
AS266702
AS266702
—
AS52279
AS52279
—
AS263739
AS263739
—
AS52232
AS52232
—
AS28114
AS28114
—
AS27751
AS27751
—
AS52323
AS52323
—
AS265741
AS265741
—
AS52444
AS52444
—
AS265720
AS265720
—
AS52349
AS52349
—
AS52405
AS52405
—
AS266684
AS266684
—
AS263786
AS263786
—
AS27747
AS27747
—
AS269819
AS269819
—
AS27833
AS27833
—
AS27927
AS27927
—
AS263809
AS263809
—
AS28080
AS28080
—
AS52300
AS52300
—
AS264738
AS264738
—
AS52307
AS52307
—
AS61510
AS61510
—
AS27987
AS27987
—
| Prefix | Name | Country |
|---|---|---|
| 131.0.104.0/22 | AS22927 | — |
| 168.226.0.0/16 | AS22927 | — |
| 168.226.214.0/24 | AS22927 | — |
| 168.226.217.0/24 | AS22927 | — |
| 168.226.218.0/23 | AS22927 | — |
| 168.226.35.0/24 | AS22927 | — |
| 168.226.55.0/24 | AS22927 | — |
| 168.226.56.0/22 | AS22927 | — |
| 168.226.80.0/21 | AS22927 | — |
| 168.226.88.0/22 | AS22927 | — |
| 168.226.92.0/22 | AS22927 | — |
| 179.36.0.0/14 | AS22927 | — |
| 179.36.112.0/21 | AS22927 | — |
| 179.36.240.0/21 | AS22927 | — |
| 179.36.96.0/20 | AS22927 | — |
| 179.37.0.0/17 | AS22927 | — |
| 179.37.128.0/18 | AS22927 | — |
| 179.37.192.0/18 | AS22927 | — |
| 179.38.0.0/17 | AS22927 | — |
| 179.38.128.0/17 | AS22927 | — |
| 179.39.0.0/17 | AS22927 | — |
| 179.39.128.0/17 | AS22927 | — |
| 179.40.0.0/15 | AS22927 | — |
| 179.40.0.0/17 | AS22927 | — |
| 179.40.24.0/24 | AS22927 | — |
| 181.20.0.0/14 | AS22927 | — |
| 181.21.28.0/22 | AS22927 | — |
| 181.21.32.0/20 | AS22927 | — |
| 181.24.0.0/14 | AS22927 | — |
| 181.25.128.0/20 | AS22927 | — |
| 181.25.144.0/22 | AS22927 | — |
| 181.25.192.0/19 | AS22927 | — |
| 181.25.32.0/20 | AS22927 | — |
| 186.100.0.0/16 | AS22927 | — |
| 186.100.0.0/17 | AS22927 | — |
| 186.128.0.0/14 | AS22927 | — |
| 186.130.130.0/24 | AS22927 | — |
| 186.130.131.0/24 | AS22927 | — |
| 186.132.0.0/14 | AS22927 | — |
| 186.134.160.0/20 | AS22927 | — |
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.
AS22927 is an autonomous system number used to identify an independently operated network. The current page associates it with Telefonica de Argentina 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 AS22927. 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 AS22927, 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.