bgpreport

Network · data from 2026-11-12

AS9325 SPARK-AS-AP - Spark New Zealand Trading Ltd

Registry name: SPARK-AS-AP - Spark New Zealand Trading Ltd, NZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9325, 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.
2403:9800:13::/48 No ROA None 636 100% 70
122.56.114.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS9325 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 83 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced79
ChangePrefix or setDetailFull-table peers
ROA: none2403:9800:13::/48No ROA covers it. Add a ROA for AS9325, maxLength 48.636 of 636
Route object: none2403:9800:13::/48No route object for it. Add a route object with origin AS9325 in the RIR database for the space.636 of 636
ROA: none122.56.114.0/24No ROA covers it. Add a ROA for AS9325, maxLength 24.671 of 673
Route object: RIR122.56.114.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

155.59.0.0/16RADBNo ROA
166.179.0.0/16RADBNo ROA
202.20.113.0/24RADBNo ROA
202.27.156.0/22RADBNo ROA
202.27.176.0/21RADBNo ROA
202.27.184.0/23RADBNo ROA
202.36.7.0/24RADBNo ROA
202.36.31.0/24RADBNo ROA
202.36.111.0/24RADBNo ROA
202.36.112.0/24RADBNo ROA
202.36.113.0/24RADBNo ROA
202.36.134.0/23RADBNo ROA
202.36.140.0/24RADBNo ROA
202.37.45.0/24RADBNo ROA
202.37.58.0/24RADBNo ROA
202.37.84.0/24RADBNo ROA
202.37.89.0/24RADBNo ROA
202.37.236.0/22RADBNo ROA
202.37.248.0/24RADBNo ROA
202.37.253.0/24RADBNo ROA
202.49.116.0/22RADBNo ROA
202.49.126.0/23RADBNo ROA
202.49.126.0/24RADBNo ROA
202.49.161.0/24RADBNo ROA
202.50.75.0/24RADBNo ROA
202.50.80.0/22RADBNo ROA
202.50.160.0/24RADBNo ROA
203.96.92.0/22RADBNo ROA
203.96.96.0/20RADBNo ROA
210.54.64.0/18RADBNo ROA
210.54.92.0/24RADBNo ROA
210.54.116.0/24RADBNo ROA
210.54.119.0/24RADBNo ROA
210.54.122.0/24RADBNo ROA
210.54.123.0/24RADBNo ROA
210.54.124.0/24RADBNo ROA
210.54.125.0/24RADBNo ROA
210.54.192.0/19RADBNo ROA
210.54.215.0/24RADBNo ROA
210.54.216.0/24RADBNo ROA
210.54.224.0/19RADBNo ROA
210.54.255.0/24RADBNo ROA
210.55.10.0/24RADBNo ROA
210.55.32.0/19RADBNo ROA
210.55.55.0/24RADBNo ROA
210.55.56.0/24RADBNo ROA
210.55.80.0/20RADBNo ROA
210.55.112.0/20RADBNo ROA
210.55.120.0/21RADBNo ROA
210.55.132.0/22RADBNo ROA
210.55.140.0/23RADBNo ROA
210.55.141.0/24RADBNo ROA
210.55.160.0/21RADBNo ROA
210.55.167.0/24RADBNo ROA
210.55.170.0/23RADBNo ROA
210.55.172.0/22RADBNo ROA
210.55.176.0/22RADBNo ROA
210.55.188.0/22RADBNo ROA
210.55.192.0/22RADBNo ROA
210.55.196.0/22RADBNo ROA
210.55.224.0/23RADBNo ROA
210.55.235.0/24RADBNo ROA
210.55.236.0/22RADBNo ROA
210.55.248.0/22RADBNo ROA
210.55.252.0/24RADBNo ROA
210.86.0.0/18RADBNo ROA
210.86.5.0/24RADBNo ROA
210.86.6.0/23RADBNo ROA
210.86.8.0/21RADBNo ROA
210.86.16.0/23RADBNo ROA
210.86.19.0/24RADBNo ROA
219.88.0.0/17RADBNo ROA
219.88.102.0/23RADBNo ROA
219.88.104.0/21RADBNo ROA
219.88.108.0/24RADBNo ROA
219.88.112.0/20RADBNo ROA
219.88.121.0/24RADBNo ROA
219.89.79.0/24RADBNo ROA
219.89.111.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.