Country
—
ASN LANDING PAGE
TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited
Last updated · Apr 4, 2026
Country
—
Total prefixes
2290
IPv4 prefixes
2243
IPv6 prefixes
47
TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited currently shows 2290 prefixes and 19 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.
TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited 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.
Detailed data for this ASN is not available right now.
| Prefix | Name | Country |
|---|---|---|
| 1.116.0.0/15 | AS45090 | — |
| 1.116.0.0/18 | AS45090 | — |
| 1.116.128.0/18 | AS45090 | — |
| 1.116.192.0/18 | AS45090 | — |
| 1.116.64.0/18 | AS45090 | — |
| 1.117.0.0/18 | AS45090 | — |
| 1.117.128.0/18 | AS45090 | — |
| 1.117.192.0/18 | AS45090 | — |
| 1.117.64.0/18 | AS45090 | — |
| 1.12.0.0/14 | AS45090 | — |
| 1.12.0.0/18 | AS45090 | — |
| 1.12.0.0/20 | AS45090 | — |
| 1.12.128.0/18 | AS45090 | — |
| 1.12.14.0/23 | AS45090 | — |
| 1.12.192.0/18 | AS45090 | — |
| 1.12.34.0/23 | AS45090 | — |
| 1.12.64.0/18 | AS45090 | — |
| 1.13.0.0/18 | AS45090 | — |
| 1.13.128.0/18 | AS45090 | — |
| 1.13.192.0/18 | AS45090 | — |
| 1.13.64.0/18 | AS45090 | — |
| 1.14.0.0/18 | AS45090 | — |
| 1.14.128.0/18 | AS45090 | — |
| 1.14.192.0/18 | AS45090 | — |
| 1.14.64.0/18 | AS45090 | — |
| 1.15.0.0/18 | AS45090 | — |
| 1.15.128.0/18 | AS45090 | — |
| 1.15.192.0/18 | AS45090 | — |
| 1.15.64.0/18 | AS45090 | — |
| 101.33.128.0/17 | AS45090 | — |
| 101.33.144.0/22 | AS45090 | — |
| 101.33.148.0/22 | AS45090 | — |
| 101.33.152.0/22 | AS45090 | — |
| 101.33.156.0/22 | AS45090 | — |
| 101.33.160.0/22 | AS45090 | — |
| 101.33.164.0/22 | AS45090 | — |
| 101.33.168.0/22 | AS45090 | — |
| 101.33.172.0/22 | AS45090 | — |
| 101.33.176.0/22 | AS45090 | — |
| 101.33.180.0/22 | AS45090 | — |
Helpful for comparing AliDNS, Anycast DNS, and broader Alibaba cloud-network ownership.
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.
Continue from this ASN into cloud-provider, hosting, and VPS ownership analysis.
Useful for deciding whether this ASN looks more like cloud infrastructure or traditional website hosting.
Useful for placing this ASN into datacenter-versus-residential attribution analysis.
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.
AS45090 is an autonomous system number used to identify an independently operated network. The current page associates it with TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited 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 AS45090. 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 AS45090, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Determine whether an IP belongs to AWS, Google Cloud, Azure, or another cloud network by combining ASN, WHOIS, prefixes, and organization data.
Separate cloud-server IPs, traditional web-hosting IPs, shared-hosting IPs, and website-hosting networks through ASN, WHOIS, organization, and deployment signals.
Determine whether an IP looks more like VPS, cloud hosting, dedicated server, or hosted datacenter infrastructure through ASN, WHOIS, and network signals.
Understand how dedicated-server IPs differ from cloud-server IPs through ASN, WHOIS, prefixes, and hosting-network signals.