Country
—
ASN LANDING PAGE
AS38064
NZ-AS-NS1-AP ASN for anycast peering of
Last updated · Apr 4, 2026
Total prefixes
12
IPv4 prefixes
3
IPv6 prefixes
9
ASN summary
How to read the scale of AS38064
NZ-AS-NS1-AP ASN for anycast peering of currently shows 12 prefixes and 7 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS38064?
NZ-AS-NS1-AP ASN for anycast peering of 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.
What should you inspect next after the AS38064 page?
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.
Search intents this ASN page helps cover
AS38064 ASN lookupAS38064 BGPAS38064 peersAS38064 prefixesAS38064 upstreamsNZ-AS-NS1-AP ASN for anycast peering of ASNCDN ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 2001:dce:100::/48 | AS38064 | — |
| 2001:dce:5100::/48 | AS38064 | — |
| 2001:dce:5200::/48 | AS38064 | — |
| 2001:dce:7000::/48 | AS38064 | — |
| 2001:dce:7800::/48 | AS38064 | — |
| 2001:dce:8800::/48 | AS38064 | — |
| 2001:dce:9500::/48 | AS38064 | — |
| 2001:dce:d452::/48 | AS38064 | — |
| 2001:dce:d454::/48 | AS38064 | — |
| 202.46.184.0/24 | AS38064 | — |
| 202.46.185.0/24 | AS38064 | — |
| 202.46.189.0/24 | AS38064 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
CDN, Anycast, and Edge Network Guide
Useful when you want to decide whether this ASN behaves like a CDN, Anycast, or edge-delivery network.
Website CDN vs Origin Hosting Detection Guide
Useful for deciding whether this ASN looks more like website CDN frontage or the real hosting origin.
How to Find the Real Hosting Provider Guide
Useful for tracing the real hosting provider behind an edge or CDN layer.
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
Frequently asked questions about this ASN page
What does AS38064 represent?
AS38064 is an autonomous system number used to identify an independently operated network. The current page associates it with NZ-AS-NS1-AP ASN for anycast peering of in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS38064 page?
They help explain the scale, interconnection depth, and route structure of AS38064. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS38064?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS38064, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
Public DNS vs CDN and Anycast Guide
Separate public DNS, CDN Anycast, and edge-delivery IP behavior, especially when one IP appears to shift across multiple locations.
CDN, Anycast, and Edge Network Guide
Understand how CDN, Anycast, and edge delivery change IP geolocation, latency interpretation, origin tracing, and ASN attribution.
Website CDN vs Origin Hosting Detection Guide
Separate CDN or edge IPs from the real website origin-hosting or server IP behind a domain.
How to Find the Real Hosting Provider Guide
Use DNS, ASN, WHOIS, CNAMEs, HTTP headers, and CDN clues to trace the real hosting or cloud provider behind a website.