Country
—
ASN LANDING PAGE
Telecom Argentina S.A.
Last updated · Apr 10, 2026
Country
—
Total prefixes
789
IPv4 prefixes
689
IPv6 prefixes
100
Telecom Argentina S.A. currently shows 789 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.
Telecom Argentina 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.
AS4270
AS4270
—
AS27768
AS27768
—
AS27787
AS27787
—
AS27983
AS27983
—
AS27895
AS27895
—
AS10481
AS10481
—
AS27813
AS27813
—
AS263774
AS263774
—
AS28075
AS28075
—
AS28048
AS28048
—
AS52328
AS52328
—
AS263684
AS263684
—
AS263809
AS263809
—
AS52275
AS52275
—
AS262229
AS262229
—
AS264642
AS264642
—
AS263776
AS263776
—
AS27971
AS27971
—
AS52312
AS52312
—
AS52323
AS52323
—
AS263812
AS263812
—
AS22927
AS22927
—
AS265686
AS265686
—
AS52371
AS52371
—
AS13585
AS13585
—
AS52486
AS52486
—
AS262150
AS262150
—
AS264852
AS264852
—
AS27823
AS27823
—
AS52440
AS52440
—
AS266769
AS266769
—
AS267876
AS267876
—
AS264848
AS264848
—
AS262156
AS262156
—
AS7005
AS7005
—
AS26621
AS26621
—
AS266752
AS266752
—
AS265798
AS265798
—
AS269874
AS269874
—
AS61517
AS61517
—
| Prefix | Name | Country |
|---|---|---|
| 152.168.0.0/14 | AS7303 | — |
| 152.168.0.0/15 | AS7303 | — |
| 152.168.0.0/16 | AS7303 | — |
| 152.169.0.0/16 | AS7303 | — |
| 152.170.0.0/15 | AS7303 | — |
| 152.170.0.0/16 | AS7303 | — |
| 152.171.0.0/16 | AS7303 | — |
| 170.231.136.0/22 | AS7303 | — |
| 181.0.0.0/12 | AS7303 | — |
| 181.0.0.0/15 | AS7303 | — |
| 181.0.0.0/16 | AS7303 | — |
| 181.0.0.0/17 | AS7303 | — |
| 181.0.0.0/18 | AS7303 | — |
| 181.0.128.0/17 | AS7303 | — |
| 181.0.128.0/18 | AS7303 | — |
| 181.0.192.0/18 | AS7303 | — |
| 181.0.64.0/18 | AS7303 | — |
| 181.1.0.0/16 | AS7303 | — |
| 181.1.0.0/17 | AS7303 | — |
| 181.1.0.0/18 | AS7303 | — |
| 181.1.0.0/19 | AS7303 | — |
| 181.1.128.0/20 | AS7303 | — |
| 181.1.128.0/21 | AS7303 | — |
| 181.1.136.0/21 | AS7303 | — |
| 181.1.144.0/21 | AS7303 | — |
| 181.1.156.0/22 | AS7303 | — |
| 181.1.160.0/19 | AS7303 | — |
| 181.1.160.0/20 | AS7303 | — |
| 181.1.176.0/20 | AS7303 | — |
| 181.1.192.0/18 | AS7303 | — |
| 181.1.192.0/19 | AS7303 | — |
| 181.1.224.0/19 | AS7303 | — |
| 181.1.32.0/19 | AS7303 | — |
| 181.1.64.0/18 | AS7303 | — |
| 181.1.64.0/19 | AS7303 | — |
| 181.1.96.0/19 | AS7303 | — |
| 181.10.0.0/15 | AS7303 | — |
| 181.10.0.0/16 | AS7303 | — |
| 181.10.117.0/24 | AS7303 | — |
| 181.10.194.0/24 | AS7303 | — |
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.
AS7303 is an autonomous system number used to identify an independently operated network. The current page associates it with Telecom Argentina 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 AS7303. 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 AS7303, 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.