Country
—
ASN LANDING PAGE
CHINANET-SH-AP China Telecom Group
Last updated · Apr 4, 2026
Country
—
Total prefixes
601
IPv4 prefixes
502
IPv6 prefixes
99
CHINANET-SH-AP China Telecom Group currently shows 601 prefixes and 42 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.
CHINANET-SH-AP China Telecom Group 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.
AS17775
AS17775
—
AS9812
AS9812
—
AS146812
AS146812
—
AS23853
AS23853
—
AS139179
AS139179
—
AS45061
AS45061
—
AS151313
AS151313
—
AS17428
AS17428
—
AS10100
AS10100
—
AS137715
AS137715
—
AS59083
AS59083
—
AS139148
AS139148
—
AS56006
AS56006
—
AS137758
AS137758
—
AS4249
AS4249
—
AS131536
AS131536
—
AS24427
AS24427
—
AS40526
AS40526
—
AS24424
AS24424
—
AS139138
AS139138
—
AS137746
AS137746
—
AS32528
AS32528
—
AS1766
AS1766
—
AS26380
AS26380
—
AS63617
AS63617
—
AS137806
AS137806
—
AS63580
AS63580
—
AS109
AS109
—
AS17739
AS17739
—
AS135432
AS135432
—
AS38375
AS38375
—
AS38381
AS38381
—
AS63570
AS63570
—
AS151247
AS151247
—
AS56000
AS56000
—
AS56013
AS56013
—
AS58536
AS58536
—
AS59073
AS59073
—
AS55996
AS55996
—
AS63641
AS63641
—
| Prefix | Name | Country |
|---|---|---|
| 101.224.0.0/13 | AS4812 | — |
| 101.226.0.0/16 | AS4812 | — |
| 101.226.186.0/23 | AS4812 | — |
| 101.226.188.0/22 | AS4812 | — |
| 101.226.192.0/22 | AS4812 | — |
| 101.227.0.0/16 | AS4812 | — |
| 101.228.0.0/17 | AS4812 | — |
| 101.228.0.0/19 | AS4812 | — |
| 101.228.32.0/19 | AS4812 | — |
| 101.228.64.0/19 | AS4812 | — |
| 101.228.96.0/19 | AS4812 | — |
| 101.230.0.0/15 | AS4812 | — |
| 101.230.0.0/16 | AS4812 | — |
| 101.230.128.0/18 | AS4812 | — |
| 101.230.152.0/24 | AS4812 | — |
| 101.230.155.0/24 | AS4812 | — |
| 101.230.177.0/24 | AS4812 | — |
| 101.230.215.0/24 | AS4812 | — |
| 101.230.226.0/24 | AS4812 | — |
| 101.230.250.0/24 | AS4812 | — |
| 101.230.253.0/24 | AS4812 | — |
| 101.230.64.0/18 | AS4812 | — |
| 101.230.80.0/20 | AS4812 | — |
| 101.231.0.0/16 | AS4812 | — |
| 101.231.121.0/24 | AS4812 | — |
| 101.231.36.0/24 | AS4812 | — |
| 101.80.0.0/13 | AS4812 | — |
| 101.82.0.0/15 | AS4812 | — |
| 101.87.0.0/16 | AS4812 | — |
| 101.88.0.0/13 | AS4812 | — |
| 101.90.0.0/16 | AS4812 | — |
| 101.95.144.0/24 | AS4812 | — |
| 101.96.10.0/23 | AS4812 | — |
| 103.108.244.0/24 | AS4812 | — |
| 103.116.76.0/24 | AS4812 | — |
| 103.116.77.0/24 | AS4812 | — |
| 103.116.78.0/24 | AS4812 | — |
| 103.144.158.0/24 | AS4812 | — |
| 103.147.124.0/24 | AS4812 | — |
| 103.152.56.0/23 | AS4812 | — |
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.
AS4812 is an autonomous system number used to identify an independently operated network. The current page associates it with CHINANET-SH-AP China Telecom Group 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 AS4812. 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 AS4812, 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.