bgpreport

Network · data from 2026-11-12

AS4770 Internet Company of New Zealand Ltd

Registry name: ICONZ-AS - ICONZ Ltd, NZ · PeeringDB

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

Announced routes

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

210.56.32.0/24 Invalid: maxLength Nonecovered by 210.56.32.0/20 65 10%low visibility 33
210.185.63.0/24 Invalid: maxLength Nonecovered by 210.185.0.0/18 65 10%low visibility 33
210.48.17.0/24 Invalid: maxLength Nonecovered by 210.48.0.0/17 41 6%low visibility 26
210.48.22.0/24 Invalid: maxLength Nonecovered by 210.48.0.0/17 41 6%low visibility 26
210.48.24.0/24 Invalid: maxLength Nonecovered by 210.48.0.0/17 41 6%low visibility 26
202.37.144.0/21 Valid RIR databaseAPNIC, RADB 672 100% 67
103.116.188.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
202.37.140.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
202.37.200.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
202.37.224.0/21 Valid RIR databaseAPNIC, RADB 671 100% 68
202.41.136.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
202.74.224.0/21 Valid RIR databaseAPNIC, RADB 671 100% 68
210.48.0.0/17 Valid RIR databaseAPNIC, RADB 671 100% 68
210.185.0.0/18 Valid RIR databaseAPNIC, RADB 671 100% 68
210.56.32.0/20 Valid RIR databaseAPNIC, RADB 670 100% 67
2405:6000::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2001:df5:5d00::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS4770's PeeringDB record names no 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 32 are in fix.csv.

  • ROA: maxLength5
  • Route object: none5
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: maxLength210.56.32.0/24ROA 210.56.32.0/20 AS4770 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 210.56.32.0/24.65 of 673
Route object: none210.56.32.0/24No route object for it. A route object for 210.56.32.0/20 with origin AS4770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4770 in the RIR database for the space.65 of 673
ROA: maxLength210.185.63.0/24ROA 210.185.0.0/18 AS4770 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 210.185.63.0/24.65 of 673
Route object: none210.185.63.0/24No route object for it. A route object for 210.185.0.0/18 with origin AS4770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4770 in the RIR database for the space.65 of 673
ROA: maxLength210.48.17.0/24ROA 210.48.0.0/17 AS4770 has maxLength 17; the route is a /24. Raise the maxLength, or add a ROA for 210.48.17.0/24.41 of 673
Route object: none210.48.17.0/24No route object for it. A route object for 210.48.0.0/17 with origin AS4770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4770 in the RIR database for the space.41 of 673
ROA: maxLength210.48.22.0/24ROA 210.48.0.0/17 AS4770 has maxLength 17; the route is a /24. Raise the maxLength, or add a ROA for 210.48.22.0/24.41 of 673
Route object: none210.48.22.0/24No route object for it. A route object for 210.48.0.0/17 with origin AS4770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4770 in the RIR database for the space.41 of 673
ROA: maxLength210.48.24.0/24ROA 210.48.0.0/17 AS4770 has maxLength 17; the route is a /24. Raise the maxLength, or add a ROA for 210.48.24.0/24.41 of 673
Route object: none210.48.24.0/24No route object for it. A route object for 210.48.0.0/17 with origin AS4770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4770 in the RIR database for the space.41 of 673

Route objects not announced

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

120.138.16.0/21RADBNo ROA
198.32.66.0/24RADBNo ROA
199.212.93.0/24RADBNo ROA
202.12.248.0/21RADBNo ROA
202.14.100.0/24APNIC, RADBValid
202.36.36.0/22APNIC, RADBValid
202.37.73.0/24RADBNo ROA
202.37.76.0/24RADBNo ROA
202.37.85.0/24RADBNo ROA
202.37.163.0/24RADBNo ROA
202.37.240.0/23RADBNo ROA
202.37.252.0/23RADBNo ROA
202.49.62.0/24RADBNo ROA
202.50.87.0/24RADBNo ROA
202.50.139.0/24RADBNo ROA
202.55.96.0/20RADBNo ROA
205.233.128.0/21RADBNo ROA
205.233.136.0/23RADBNo ROA
210.54.136.0/22RADBNo ROA
210.54.140.0/24RADBNo ROA
210.54.160.0/19RADBNo ROA
210.55.24.0/22RADBNo 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.