Country
—
ASN LANDING PAGE
GUO-AS - Chengjie Guo
Last updated · Apr 4, 2026
Country
—
Total prefixes
14
IPv4 prefixes
0
IPv6 prefixes
14
GUO-AS - Chengjie Guo currently shows 14 prefixes and 22 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.
GUO-AS - Chengjie Guo 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.
AS34927
AS34927
—
AS44324
AS44324
—
AS215467
AS215467
—
AS38008
AS38008
—
AS20473
AS20473
—
AS209533
AS209533
—
AS7720
AS7720
—
AS53356
AS53356
—
AS207108
AS207108
—
AS29632
AS29632
—
AS8772
AS8772
—
AS393577
AS393577
—
AS8298
AS8298
—
AS50869
AS50869
—
AS924
AS924
—
AS39351
AS39351
—
AS47498
AS47498
—
AS58299
AS58299
—
AS61049
AS61049
—
AS209022
AS209022
—
AS209823
AS209823
—
AS212635
AS212635
—
| Prefix | Name | Country |
|---|---|---|
| 2a0a:6040:d600::/44 | AS200936 | — |
| 2a0a:6040:d610::/48 | AS200936 | — |
| 2a0a:6040:d611::/48 | AS200936 | — |
| 2a0a:6040:d612::/48 | AS200936 | — |
| 2a0a:6040:d613::/48 | AS200936 | — |
| 2a0a:6040:d615::/48 | AS200936 | — |
| 2a0a:6040:d618::/48 | AS200936 | — |
| 2a0a:6040:d619::/48 | AS200936 | — |
| 2a0a:6040:d623::/48 | AS200936 | — |
| 2a0a:6040:d624::/48 | AS200936 | — |
| 2a0a:6040:d626::/48 | AS200936 | — |
| 2a0a:6040:d629::/48 | AS200936 | — |
| 2a0f:1cc5:1901::/48 | AS200936 | — |
| 2a0f:9400:6110::/48 | AS200936 | — |
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.
AS200936 is an autonomous system number used to identify an independently operated network. The current page associates it with GUO-AS - Chengjie Guo 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 AS200936. 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 AS200936, 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.