Country
—
ASN LANDING PAGE
REANNZ-NZ-AP REANNZ National Research and Education Network
Last updated · Apr 4, 2026
Country
—
Total prefixes
14
IPv4 prefixes
11
IPv6 prefixes
3
REANNZ-NZ-AP REANNZ National Research and Education Network currently shows 14 prefixes and 57 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.
REANNZ-NZ-AP REANNZ National Research and Education Network 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.
AS38299
AS38299
—
AS23905
AS23905
—
AS38626
AS38626
—
AS55747
AS55747
—
AS9432
AS9432
—
AS9431
AS9431
—
AS24398
AS24398
—
AS10110
AS10110
—
AS38305
AS38305
—
AS38319
AS38319
—
AS132264
AS132264
—
AS45138
AS45138
—
AS45787
AS45787
—
AS9483
AS9483
—
AS38473
AS38473
—
AS131272
AS131272
—
AS133928
AS133928
—
AS135288
AS135288
—
AS55524
AS55524
—
AS139272
AS139272
—
AS681
AS681
—
AS4667
AS4667
—
AS17542
AS17542
—
AS38906
AS38906
—
AS131187
AS131187
—
AS135431
AS135431
—
AS9433
AS9433
—
AS55702
AS55702
—
AS133857
AS133857
—
AS134227
AS134227
—
AS55746
AS55746
—
AS55485
AS55485
—
AS18378
AS18378
—
AS7500
AS7500
—
AS3356
AS3356
—
AS6939
AS6939
—
AS135069
AS135069
—
AS11537
AS11537
—
AS137409
AS137409
—
AS9002
AS9002
—
AS1828
AS1828
—
AS24115
AS24115
—
AS24482
AS24482
—
AS35280
AS35280
—
AS36236
AS36236
—
AS49544
AS49544
—
AS2907
AS2907
—
AS8888
AS8888
—
AS61138
AS61138
—
AS132847
AS132847
—
AS18106
AS18106
—
AS64073
AS64073
—
AS52025
AS52025
—
AS34927
AS34927
—
AS35889
AS35889
—
AS7575
AS7575
—
AS394256
AS394256
—
| Prefix | Name | Country |
|---|---|---|
| 163.7.128.0/19 | AS38022 | — |
| 163.7.136.0/24 | AS38022 | — |
| 163.7.144.0/21 | AS38022 | — |
| 163.7.159.0/24 | AS38022 | — |
| 202.27.240.0/23 | AS38022 | — |
| 202.27.242.0/24 | AS38022 | — |
| 202.27.243.0/24 | AS38022 | — |
| 202.36.85.0/24 | AS38022 | — |
| 202.50.199.0/24 | AS38022 | — |
| 202.50.205.0/24 | AS38022 | — |
| 210.7.32.0/20 | AS38022 | — |
| 2404:138::/32 | AS38022 | — |
| 2404:139::/32 | AS38022 | — |
| 2404:139::/48 | AS38022 | — |
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.
AS38022 is an autonomous system number used to identify an independently operated network. The current page associates it with REANNZ-NZ-AP REANNZ National Research and Education Network 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 AS38022. 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 AS38022, 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.