bgpreport

Network · data from 2026-11-12

AS38495 TRANSPOWER-B-AS-AP - Transpower New Zealand Ltd.

Registry name: TRANSPOWER-B-AS-AP - Transpower New Zealand Ltd., AU · not in PeeringDB

8IPv4 routes 75.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS38495, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38495, 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.
166.65.176.0/20 No ROA Nonecovered by 166.65.0.0/16 671 100% 66
166.65.192.0/20 No ROA Nonecovered by 166.65.0.0/16 671 100% 66
166.65.180.0/22 Valid RIR databaseAPNIC 673 100% 70
166.65.184.0/21 Valid RIR databaseAPNIC, RADB 673 100% 70
166.65.192.0/21 Valid RIR databaseAPNIC 673 100% 70
166.65.208.0/20 Valid RIR databaseAPNIC 673 100% 70
166.65.11.0/24 Valid RIR databaseAPNIC 671 100% 66
166.65.16.0/20 Valid RIR databaseAPNIC 671 100% 66

AS-SET

AS38495 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 14 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none166.65.176.0/20No ROA covers it. Add a ROA for AS38495, maxLength 20.671 of 673
Route object: none166.65.176.0/20No route object for it. A route object for 166.65.0.0/16 with origin AS38495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38495 in the RIR database for the space.671 of 673
ROA: none166.65.192.0/20No ROA covers it. Add a ROA for AS38495, maxLength 20.671 of 673
Route object: none166.65.192.0/20No route object for it. A route object for 166.65.0.0/16 with origin AS38495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38495 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS38495 whose prefix no peer sees AS38495 announce. Many are kept on purpose (backup routes, space announced only in some places).

166.65.0.0/16RADBNo ROA
166.65.176.0/22APNICValid
166.65.180.0/23APNICValid
166.65.182.0/23APNICValid
166.65.184.0/22APNIC, RADBValid
166.65.188.0/22APNIC, RADBValid
166.65.192.0/22APNICValid
166.65.196.0/22APNICValid
166.65.200.0/21APNICValid
192.195.219.0/24RADBNo 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.