Country
—
ASN LANDING PAGE
CONE - CyrusOne LLC
Last updated · Apr 4, 2026
Country
—
Total prefixes
176
IPv4 prefixes
166
IPv6 prefixes
10
CONE - CyrusOne LLC currently shows 176 prefixes and 56 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.
CONE - CyrusOne LLC 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.
AS26351
AS26351
—
AS21945
AS21945
—
AS25765
AS25765
—
AS400615
AS400615
—
AS2165
AS2165
—
AS46202
AS46202
—
AS14032
AS14032
—
AS397325
AS397325
—
AS393571
AS393571
—
AS46696
AS46696
—
AS401985
AS401985
—
AS396940
AS396940
—
AS36328
AS36328
—
AS19
AS19
—
AS30423
AS30423
—
AS19137
AS19137
—
AS396936
AS396936
—
AS16391
AS16391
—
AS60269
AS60269
—
AS10848
AS10848
—
AS18649
AS18649
—
AS11189
AS11189
—
AS25907
AS25907
—
AS18676
AS18676
—
AS394122
AS394122
—
AS30673
AS30673
—
AS396285
AS396285
—
AS63474
AS63474
—
AS19787
AS19787
—
AS3828
AS3828
—
AS22334
AS22334
—
AS10511
AS10511
—
AS398492
AS398492
—
AS16678
AS16678
—
AS18689
AS18689
—
AS21961
AS21961
—
AS40062
AS40062
—
AS53305
AS53305
—
AS53396
AS53396
—
AS53562
AS53562
—
| Prefix | Name | Country |
|---|---|---|
| 139.60.112.0/24 | AS62 | — |
| 139.60.113.0/24 | AS62 | — |
| 140.162.8.0/22 | AS62 | — |
| 167.253.57.0/24 | AS62 | — |
| 192.196.240.0/20 | AS62 | — |
| 192.203.96.0/24 | AS62 | — |
| 192.75.58.0/24 | AS62 | — |
| 198.136.250.0/24 | AS62 | — |
| 198.22.239.0/24 | AS62 | — |
| 198.22.240.0/24 | AS62 | — |
| 198.32.126.0/23 | AS62 | — |
| 198.32.131.0/24 | AS62 | — |
| 198.32.136.0/21 | AS62 | — |
| 198.32.145.0/24 | AS62 | — |
| 198.32.147.0/24 | AS62 | — |
| 198.32.148.0/22 | AS62 | — |
| 198.32.152.0/21 | AS62 | — |
| 198.32.16.0/20 | AS62 | — |
| 198.32.164.0/24 | AS62 | — |
| 198.32.166.0/23 | AS62 | — |
| 198.32.168.0/22 | AS62 | — |
| 198.32.172.0/23 | AS62 | — |
| 198.32.174.0/24 | AS62 | — |
| 198.32.180.0/24 | AS62 | — |
| 198.32.184.0/23 | AS62 | — |
| 198.32.187.0/24 | AS62 | — |
| 198.32.188.0/23 | AS62 | — |
| 198.32.193.0/24 | AS62 | — |
| 198.32.197.0/24 | AS62 | — |
| 198.32.198.0/23 | AS62 | — |
| 198.32.200.0/21 | AS62 | — |
| 198.32.200.0/24 | AS62 | — |
| 198.32.208.0/20 | AS62 | — |
| 198.32.240.0/24 | AS62 | — |
| 198.32.244.0/22 | AS62 | — |
| 198.32.248.0/21 | AS62 | — |
| 198.32.32.0/19 | AS62 | — |
| 198.32.64.0/19 | AS62 | — |
| 198.32.8.0/21 | AS62 | — |
| 198.58.73.0/24 | AS62 | — |
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.
AS62 is an autonomous system number used to identify an independently operated network. The current page associates it with CONE - CyrusOne LLC 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 AS62. 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 AS62, 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.