Country
—
ASN LANDING PAGE
SD-DATA-CENTER - SD Data Center
Last updated · Apr 4, 2026
Country
—
Total prefixes
39
IPv4 prefixes
28
IPv6 prefixes
11
SD-DATA-CENTER - SD Data Center currently shows 39 prefixes and 49 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.
SD-DATA-CENTER - SD Data Center 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.
AS174
AS174
—
AS6461
AS6461
—
AS33363
AS33363
—
AS6939
AS6939
—
AS3257
AS3257
—
AS2914
AS2914
—
AS3356
AS3356
—
AS396998
AS396998
—
AS3303
AS3303
—
AS37468
AS37468
—
AS64073
AS64073
—
AS1103
AS1103
—
AS8298
AS8298
—
AS137409
AS137409
—
AS4826
AS4826
—
AS4230
AS4230
—
AS35280
AS35280
—
AS6057
AS6057
—
AS1828
AS1828
—
AS6204
AS6204
—
AS7018
AS7018
—
AS7195
AS7195
—
AS7575
AS7575
—
AS13786
AS13786
—
AS17639
AS17639
—
AS19151
AS19151
—
AS20080
AS20080
—
AS24482
AS24482
—
AS36236
AS36236
—
AS37721
AS37721
—
AS49544
AS49544
—
AS52320
AS52320
—
AS60171
AS60171
—
AS61573
AS61573
—
AS64126
AS64126
—
AS132847
AS132847
—
AS263237
AS263237
—
AS3399
AS3399
—
AS12552
AS12552
—
AS50763
AS50763
—
| Prefix | Name | Country |
|---|---|---|
| 103.102.8.0/22 | AS13984 | — |
| 162.217.148.0/22 | AS13984 | — |
| 164.153.0.0/20 | AS13984 | — |
| 173.227.128.0/22 | AS13984 | — |
| 173.227.128.0/24 | AS13984 | — |
| 193.25.186.0/23 | AS13984 | — |
| 205.149.128.0/20 | AS13984 | — |
| 205.149.134.0/23 | AS13984 | — |
| 205.149.143.0/24 | AS13984 | — |
| 206.124.171.0/24 | AS13984 | — |
| 206.124.173.0/24 | AS13984 | — |
| 206.124.190.0/24 | AS13984 | — |
| 208.234.168.0/23 | AS13984 | — |
| 209.114.192.0/19 | AS13984 | — |
| 209.151.192.0/22 | AS13984 | — |
| 209.151.196.0/22 | AS13984 | — |
| 209.151.197.0/24 | AS13984 | — |
| 209.151.198.0/24 | AS13984 | — |
| 209.151.199.0/24 | AS13984 | — |
| 209.151.200.0/22 | AS13984 | — |
| 209.151.217.0/24 | AS13984 | — |
| 209.151.218.0/23 | AS13984 | — |
| 216.213.100.0/23 | AS13984 | — |
| 216.213.102.0/23 | AS13984 | — |
| 216.213.96.0/23 | AS13984 | — |
| 2401:dac0::/32 | AS13984 | — |
| 2604:2ec0:1000::/36 | AS13984 | — |
| 2604:2ec0:2000::/36 | AS13984 | — |
| 2604:2ec0:200::/40 | AS13984 | — |
| 2604:2ec0:3000::/36 | AS13984 | — |
| 2604:2ec0:300::/40 | AS13984 | — |
| 2604:2ec0:7000::/36 | AS13984 | — |
| 2604:2ec0:700::/40 | AS13984 | — |
| 2604:2ec0::/32 | AS13984 | — |
| 2604:2ec0::/40 | AS13984 | — |
| 2a09:6d80::/32 | AS13984 | — |
| 63.144.240.0/24 | AS13984 | — |
| 74.117.144.0/22 | AS13984 | — |
| 8.34.27.0/24 | AS13984 | — |
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.
AS13984 is an autonomous system number used to identify an independently operated network. The current page associates it with SD-DATA-CENTER - SD Data Center 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 AS13984. 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 AS13984, 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.