Country
—
ASN LANDING PAGE
APNIC-COLO Asia Pacific Network Information Centre
Last updated · Apr 4, 2026
Country
—
Total prefixes
4
IPv4 prefixes
2
IPv6 prefixes
2
APNIC-COLO Asia Pacific Network Information Centre currently shows 4 prefixes and 45 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.
APNIC-COLO Asia Pacific Network Information Centre 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.
AS2497
AS2497
—
AS2516
AS2516
—
AS6939
AS6939
—
AS4713
AS4713
—
AS13335
AS13335
—
AS3491
AS3491
—
AS32787
AS32787
—
AS137409
AS137409
—
AS23764
AS23764
—
AS2500
AS2500
—
AS58453
AS58453
—
AS1828
AS1828
—
AS136106
AS136106
—
AS35280
AS35280
—
AS55685
AS55685
—
AS137367
AS137367
—
AS20473
AS20473
—
AS2907
AS2907
—
AS17408
AS17408
—
AS38158
AS38158
—
AS140570
AS140570
—
AS24482
AS24482
—
AS101
AS101
—
AS8220
AS8220
—
AS15830
AS15830
—
AS10010
AS10010
—
AS59105
AS59105
—
AS36236
AS36236
—
AS21859
AS21859
—
AS134148
AS134148
—
AS138997
AS138997
—
AS137207
AS137207
—
AS38082
AS38082
—
AS55805
AS55805
—
AS9607
AS9607
—
AS7529
AS7529
—
AS9354
AS9354
—
AS4862
AS4862
—
AS138915
AS138915
—
AS7506
AS7506
—
| Prefix | Name | Country |
|---|---|---|
| 2001:dc0::/35 | AS4777 | — |
| 2001:dc0:c000::/35 | AS4777 | — |
| 202.12.28.0/24 | AS4777 | — |
| 203.119.0.0/24 | AS4777 | — |
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.
AS4777 is an autonomous system number used to identify an independently operated network. The current page associates it with APNIC-COLO Asia Pacific Network Information Centre 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 AS4777. 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 AS4777, 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.