Network · data from 2026-11-12
AS132264 CALLAGHAN-INNOVATION-AS-AP - Callaghan Innovation
Registry name: CALLAGHAN-INNOVATION-AS-AP - Callaghan Innovation, NZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132264, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 161.65.172.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 161.65.173.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 131.203.8.0/21 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 131.203.18.0/23 | Valid | RIR databaseAPNIC, RADB | 668 99% |
AS-SET
AS132264 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 65 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced61
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 161.65.172.0/24 | No ROA covers it. Add a ROA for AS132264, maxLength 24. |
| Route object: RIR | 161.65.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 161.65.173.0/24 | No ROA covers it. Add a ROA for AS132264, maxLength 24. |
| Route object: RIR | 161.65.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132264 whose prefix no peer sees AS132264 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.203.8.0/22 | APNIC | Valid |
| 131.203.8.0/23 | APNIC | Valid |
| 131.203.8.0/24 | APNIC | Valid |
| 131.203.9.0/24 | APNIC | Valid |
| 131.203.10.0/23 | APNIC | Valid |
| 131.203.10.0/24 | APNIC | Valid |
| 131.203.11.0/24 | APNIC | Valid |
| 131.203.12.0/22 | APNIC | Valid |
| 131.203.12.0/23 | APNIC | Valid |
| 131.203.12.0/24 | APNIC | Valid |
| 131.203.13.0/24 | APNIC | Valid |
| 131.203.14.0/23 | APNIC | Valid |
| 131.203.14.0/24 | APNIC | Valid |
| 131.203.15.0/24 | APNIC | Valid |
| 131.203.16.0/22 | APNIC | Valid |
| 131.203.16.0/23 | APNIC | Valid |
| 131.203.16.0/24 | APNIC, RADB | Valid |
| 131.203.17.0/24 | APNIC, RADB | Valid |
| 131.203.18.0/24 | APNIC | Valid |
| 131.203.19.0/24 | APNIC | Valid |
| 131.203.20.0/22 | APNIC, RADB | Valid |
| 131.203.20.0/23 | APNIC | Valid |
| 131.203.20.0/24 | APNIC, RADB | Valid |
| 131.203.21.0/24 | APNIC, RADB | Valid |
| 131.203.22.0/23 | APNIC | Valid |
| 131.203.22.0/24 | APNIC, RADB | Valid |
| 131.203.23.0/24 | APNIC, RADB | Valid |
| 131.203.24.0/22 | APNIC, RADB | Valid |
| 131.203.24.0/23 | APNIC | Valid |
| 131.203.24.0/24 | APNIC, RADB | Valid |
| 131.203.25.0/24 | APNIC, RADB | Valid |
| 131.203.26.0/23 | APNIC | Valid |
| 131.203.26.0/24 | APNIC | Valid |
| 131.203.27.0/24 | APNIC | Valid |
| 131.203.160.0/21 | APNIC, RADB | Valid |
| 131.203.160.0/22 | APNIC | Valid |
| 131.203.160.0/23 | APNIC | Valid |
| 131.203.160.0/24 | APNIC | Valid |
| 131.203.161.0/24 | APNIC | Valid |
| 131.203.162.0/23 | APNIC | Valid |
| 131.203.162.0/24 | APNIC | Valid |
| 131.203.163.0/24 | APNIC | Valid |
| 131.203.164.0/22 | APNIC | Valid |
| 131.203.164.0/23 | APNIC | Valid |
| 131.203.164.0/24 | APNIC | Valid |
| 131.203.165.0/24 | APNIC | Valid |
| 131.203.166.0/23 | APNIC | Valid |
| 131.203.166.0/24 | APNIC | Valid |
| 131.203.167.0/24 | APNIC | Valid |
| 161.65.160.0/19 | RADB | No ROA |
| 161.65.160.0/21 | RADB | No ROA |
| 161.65.172.0/22 | RADB | No ROA |
| 161.65.174.0/24 | RADB | No ROA |
| 2401:aa80::/32 | RADB | No ROA |
| 2401:aa80::/48 | RADB | No ROA |
| 2401:aa80:1::/48 | RADB | No ROA |
| 2401:aa80:2::/48 | RADB | No ROA |
| 2401:aa80:3::/48 | RADB | No ROA |
| 2401:aa80:4::/48 | RADB | No ROA |
| 2401:aa80:5::/48 | RADB | No ROA |
| 2401:aa80:6::/48 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.