Country
—
ASN LANDING PAGE
Telmex Colombia S.A.
Last updated · Apr 10, 2026
Country
—
Total prefixes
984
IPv4 prefixes
806
IPv6 prefixes
178
Telmex Colombia S.A. currently shows 984 prefixes and 46 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.
Telmex Colombia 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.
AS10620
AS10620
—
AS26611
AS26611
—
AS265652
AS265652
—
AS270018
AS270018
—
AS264718
AS264718
—
AS263710
AS263710
—
AS262214
AS262214
—
AS28039
AS28039
—
AS264829
AS264829
—
AS274010
AS274010
—
AS8026
AS8026
—
AS263199
AS263199
—
AS263748
AS263748
—
AS271825
AS271825
—
AS264714
AS264714
—
AS27864
AS27864
—
AS266848
AS266848
—
AS273083
AS273083
—
AS267855
AS267855
—
AS264762
AS264762
—
AS266669
AS266669
—
AS269902
AS269902
—
AS3573
AS3573
—
AS274030
AS274030
—
AS52335
AS52335
—
AS272963
AS272963
—
AS2773
AS2773
—
AS3816
AS3816
—
AS200416
AS200416
—
AS7087
AS7087
—
AS15169
AS15169
—
AS18678
AS18678
—
| Prefix | Name | Country |
|---|---|---|
| 168.228.108.0/22 | AS14080 | — |
| 168.228.110.0/24 | AS14080 | — |
| 181.48.0.0/16 | AS14080 | — |
| 181.48.0.0/18 | AS14080 | — |
| 181.48.0.0/19 | AS14080 | — |
| 181.48.128.0/19 | AS14080 | — |
| 181.48.160.0/19 | AS14080 | — |
| 181.48.172.0/24 | AS14080 | — |
| 181.48.192.0/19 | AS14080 | — |
| 181.48.224.0/19 | AS14080 | — |
| 181.48.252.0/24 | AS14080 | — |
| 181.48.254.0/23 | AS14080 | — |
| 181.48.32.0/19 | AS14080 | — |
| 181.48.64.0/19 | AS14080 | — |
| 181.48.96.0/19 | AS14080 | — |
| 181.49.0.0/19 | AS14080 | — |
| 181.49.0.0/21 | AS14080 | — |
| 181.49.117.0/24 | AS14080 | — |
| 181.49.123.0/24 | AS14080 | — |
| 181.49.128.0/19 | AS14080 | — |
| 181.49.16.0/22 | AS14080 | — |
| 181.49.160.0/19 | AS14080 | — |
| 181.49.192.0/19 | AS14080 | — |
| 181.49.21.0/24 | AS14080 | — |
| 181.49.22.0/24 | AS14080 | — |
| 181.49.224.0/19 | AS14080 | — |
| 181.49.23.0/24 | AS14080 | — |
| 181.49.24.0/21 | AS14080 | — |
| 181.49.32.0/19 | AS14080 | — |
| 181.49.64.0/19 | AS14080 | — |
| 181.49.76.0/22 | AS14080 | — |
| 181.49.8.0/21 | AS14080 | — |
| 181.49.92.0/22 | AS14080 | — |
| 181.49.96.0/19 | AS14080 | — |
| 181.50.152.0/24 | AS14080 | — |
| 181.50.153.0/24 | AS14080 | — |
| 181.50.154.0/24 | AS14080 | — |
| 181.50.155.0/24 | AS14080 | — |
| 181.50.176.0/24 | AS14080 | — |
| 181.50.177.0/24 | AS14080 | — |
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.
AS14080 is an autonomous system number used to identify an independently operated network. The current page associates it with Telmex Colombia 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 AS14080. 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 AS14080, 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.