Country
—
ASN LANDING PAGE
TELECABLE DOMINICANO
Last updated · Apr 4, 2026
Country
—
Total prefixes
252
IPv4 prefixes
18
IPv6 prefixes
234
TELECABLE DOMINICANO currently shows 252 prefixes and 20 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.
TELECABLE DOMINICANO 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.
AS272027
AS272027
—
AS273217
AS273217
—
AS64134
AS64134
—
AS274072
AS274072
—
AS273838
AS273838
—
AS270098
AS270098
—
AS273844
AS273844
—
AS262221
AS262221
—
AS272882
AS272882
—
AS273961
AS273961
—
AS272813
AS272813
—
AS272908
AS272908
—
AS273861
AS273861
—
AS271988
AS271988
—
AS273824
AS273824
—
AS274157
AS274157
—
AS272962
AS272962
—
AS274159
AS274159
—
| Prefix | Name | Country |
|---|---|---|
| 149.2.82.0/23 | AS272112 | — |
| 149.2.82.0/24 | AS272112 | — |
| 149.2.83.0/24 | AS272112 | — |
| 179.49.202.0/23 | AS272112 | — |
| 179.49.202.0/24 | AS272112 | — |
| 179.49.203.0/24 | AS272112 | — |
| 2803:f10:1010::/48 | AS272112 | — |
| 2803:f10:102::/48 | AS272112 | — |
| 2803:f10:106::/48 | AS272112 | — |
| 2803:f10:107::/48 | AS272112 | — |
| 2803:f10:10::/48 | AS272112 | — |
| 2803:f10:1100::/48 | AS272112 | — |
| 2803:f10:113::/48 | AS272112 | — |
| 2803:f10:11::/48 | AS272112 | — |
| 2803:f10:124::/48 | AS272112 | — |
| 2803:f10:126::/48 | AS272112 | — |
| 2803:f10:12::/48 | AS272112 | — |
| 2803:f10:1302::/48 | AS272112 | — |
| 2803:f10:1304::/48 | AS272112 | — |
| 2803:f10:130::/48 | AS272112 | — |
| 2803:f10:1330::/48 | AS272112 | — |
| 2803:f10:1342::/48 | AS272112 | — |
| 2803:f10:134::/48 | AS272112 | — |
| 2803:f10:136::/48 | AS272112 | — |
| 2803:f10:138::/48 | AS272112 | — |
| 2803:f10:139::/48 | AS272112 | — |
| 2803:f10:13::/48 | AS272112 | — |
| 2803:f10:1400::/48 | AS272112 | — |
| 2803:f10:1401::/48 | AS272112 | — |
| 2803:f10:140::/48 | AS272112 | — |
| 2803:f10:1411::/48 | AS272112 | — |
| 2803:f10:1418::/48 | AS272112 | — |
| 2803:f10:141::/48 | AS272112 | — |
| 2803:f10:1420::/48 | AS272112 | — |
| 2803:f10:1423::/48 | AS272112 | — |
| 2803:f10:1424::/48 | AS272112 | — |
| 2803:f10:1425::/48 | AS272112 | — |
| 2803:f10:1437::/48 | AS272112 | — |
| 2803:f10:144::/48 | AS272112 | — |
| 2803:f10:14::/48 | AS272112 | — |
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.
AS272112 is an autonomous system number used to identify an independently operated network. The current page associates it with TELECABLE DOMINICANO 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 AS272112. 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 AS272112, 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.