Country
—
ASN LANDING PAGE
AS11272
Last updated · Apr 4, 2026
Country
—
Total prefixes
38
IPv4 prefixes
36
IPv6 prefixes
2
AS11272 currently shows 38 prefixes and 53 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.
AS11272 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.
AS396926
AS396926
—
AS13825
AS13825
—
AS400220
AS400220
—
AS4574
AS4574
—
AS33606
AS33606
—
AS46592
AS46592
—
AS16715
AS16715
—
AS15212
AS15212
—
AS17099
AS17099
—
AS396010
AS396010
—
AS19761
AS19761
—
AS26949
AS26949
—
AS32229
AS32229
—
AS53779
AS53779
—
AS54180
AS54180
—
AS7086
AS7086
—
AS19946
AS19946
—
AS393310
AS393310
—
AS14946
AS14946
—
AS63238
AS63238
—
AS14419
AS14419
—
AS32038
AS32038
—
AS46687
AS46687
—
AS395943
AS395943
—
AS54392
AS54392
—
AS398205
AS398205
—
AS11330
AS11330
—
AS398156
AS398156
—
AS400153
AS400153
—
AS53726
AS53726
—
AS29902
AS29902
—
AS400185
AS400185
—
AS11089
AS11089
—
AS397855
AS397855
—
AS394334
AS394334
—
AS46214
AS46214
—
AS53411
AS53411
—
AS23081
AS23081
—
AS399235
AS399235
—
AS53507
AS53507
—
| Prefix | Name | Country |
|---|---|---|
| 104.232.160.0/19 | AS11272 | — |
| 136.239.0.0/17 | AS11272 | — |
| 162.210.119.0/24 | AS11272 | — |
| 167.160.192.0/19 | AS11272 | — |
| 167.160.210.0/24 | AS11272 | — |
| 167.160.211.0/24 | AS11272 | — |
| 167.160.217.0/24 | AS11272 | — |
| 167.160.219.0/24 | AS11272 | — |
| 172.99.218.0/23 | AS11272 | — |
| 173.235.0.0/16 | AS11272 | — |
| 173.235.108.0/24 | AS11272 | — |
| 173.235.20.0/24 | AS11272 | — |
| 173.235.46.0/24 | AS11272 | — |
| 198.160.253.0/24 | AS11272 | — |
| 198.28.144.0/20 | AS11272 | — |
| 198.28.160.0/19 | AS11272 | — |
| 199.33.90.0/23 | AS11272 | — |
| 199.33.90.0/24 | AS11272 | — |
| 199.33.91.0/24 | AS11272 | — |
| 204.128.222.0/24 | AS11272 | — |
| 207.179.32.0/19 | AS11272 | — |
| 207.179.38.0/24 | AS11272 | — |
| 207.181.32.0/19 | AS11272 | — |
| 2607:f4a0:5003::/48 | AS11272 | — |
| 2607:f4a0::/32 | AS11272 | — |
| 38.140.64.0/19 | AS11272 | — |
| 50.86.0.0/16 | AS11272 | — |
| 50.86.252.0/24 | AS11272 | — |
| 50.86.62.0/24 | AS11272 | — |
| 64.28.48.0/20 | AS11272 | — |
| 66.175.128.0/18 | AS11272 | — |
| 66.175.135.0/24 | AS11272 | — |
| 67.20.0.0/20 | AS11272 | — |
| 69.57.48.0/20 | AS11272 | — |
| 69.89.208.0/20 | AS11272 | — |
| 74.113.94.0/24 | AS11272 | — |
| 76.8.224.0/19 | AS11272 | — |
| 8.42.176.0/20 | AS11272 | — |
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.
AS11272 is an autonomous system number used to identify an independently operated network. The current page associates it with AS11272 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 AS11272. 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 AS11272, 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.