Network · data from 2026-11-12

AS38299 REANNZ-CORP-NZ-AP - REANNZ Corporate

Registry name: REANNZ-CORP-NZ-AP - REANNZ Corporate, NZ · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object

6IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS38299, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38299, 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.


163.7.133.0/24	Valid	RIR databaseAPNIC, RADB	668 99%	69
210.7.40.0/24	Valid	RIR databaseAPNIC, RADB	667 99%	69
210.7.41.0/24	Valid	RIR databaseAPNIC, RADB	667 99%	69
210.7.42.0/24	Valid	RIR databaseAPNIC, RADB	667 99%	69
210.7.46.0/24	Valid	RIR databaseAPNIC, RADB	667 99%	69
210.7.47.0/24	Valid	RIR databaseAPNIC, RADB	667 99%	69
2404:138:40::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2404:138:41::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2404:138:46::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2404:138:47::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2404:138:133::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2404:138:4200::/40	Valid	RIR databaseAPNIC, RADB	635 100%	69

AS-SET

AS38299 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS38299 is announced.

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.