NZIX Outage History
NZIX is up right nowPingoru has recorded 12 incidents for NZIX: 3 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 6 of 720 (1%) |
| May 2026 | 1 | 168 of 744 (23%) |
| June 2026 | 0 | 168 of 720 (23%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 526 (0%) |
Incidents, newest first
Major May 25, 2026 Portal and OSS Outage 31d 5h Member Portal
Started May 25, 2026, 12:07 AM UTC· resolved Jun 25, 2026, 05:22 AM UTC
- investigating May 25, 2026, 12:07 AM UTC
We're aware of an incident affecting our infrastructure hosting provider, this is impacting access to our Member Portal and operational support systems. Investigations are ongoing, and we will provide an update once further information becomes available.
- monitoring May 25, 2026, 01:56 AM UTC
Our infrastructure hosting provider has advised that the outage is due to a targeted DDoS attack on their infrastructure. They have advised that services are currently operating normally for traffic routed within New Zealand. However, international traffic continues to experience degraded performance. They are continuing to work with their upstream provider on mitigation efforts, and we will provide further updates as information comes to hand.
- monitoring May 25, 2026, 03:12 AM UTC
Our infrastructure hosting provider has advised that they have applied a mitigation on the network in Sydney to address the current issue and services should now be stabilising. We are continuing to monitor the situation and will provide further updates as necessary.
- monitoring May 26, 2026, 12:40 AM UTC
Our infrastructure hosting provider has advised that they are still seeing ongoing impact from the DDoS attack, and they are working closely with their upstream providers to improve stability and connectivity. We are continuing to monitor the situation and will provide further updates as necessary.
- resolved Jun 25, 2026, 05:22 AM UTC
This incident was resolved May 27th and was not correctly closed off on our side - Apologies!
Major March 31, 2026 [PORTAL] Card Payment Failures | Merchant Issues 7h 22m Member Portal
Started Mar 31, 2026, 10:45 PM UTC· resolved Apr 01, 2026, 06:07 AM UTC
- identified Mar 31, 2026, 10:45 PM UTC
We are currently investigating an issue with our payment gateway which is causing card payments to fail, this appears to be a regression of an older issue with the merchant and fixes are underway to resolve.
- identified Apr 01, 2026, 01:27 AM UTC
The merchant has confirmed a flag on our account was missed during a recent migration with their card gateway system, the merchant is now working with the card gateway processor to resolve this urgently.
- identified Apr 01, 2026, 04:30 AM UTC
We are still waiting on a fix from our Merchant, currently no ETA at the moment but we will continue to follow up and notify of any significant changes.
- resolved Apr 01, 2026, 06:07 AM UTC
This issue has now been resolved by the merchant and payments are successfully processing.
Major October 23, 2025 [OUTAGE] CHC-IX | RS1 Down 4h 27m CHC-IX
Started Oct 23, 2025, 10:21 PM UTC· resolved Oct 24, 2025, 02:49 AM UTC
- identified Oct 23, 2025, 10:21 PM UTC
CHC-IX RS1 has encountered a hardware issue causing a crash, replacement hardware is on its way to restore the server. RS2 is unaffected.
- identified Oct 23, 2025, 11:50 PM UTC
ETA for restoration is ~1hr
- resolved Oct 24, 2025, 02:49 AM UTC
RS1 is restored after some troubleshooting firmware issues of the new hardware.
Major October 7, 2025 [OUTAGE] AKL-IX | v6 flap malformed attribute 6h 30m AKL-IX
Started Oct 07, 2025, 09:35 PM UTC· resolved Oct 08, 2025, 04:05 AM UTC
- investigating Oct 07, 2025, 09:35 PM UTC
We are currently investigating an issue that caused a flap on v6 sessions toward the route servers.
- monitoring Oct 07, 2025, 10:00 PM UTC
The offending malformed route is filtered upstream so no further impact is expected, we will place this on monitoring for now whilst work is underway to schedule emergency upgrades to the route servers to avoid this in the future. The root cause appears to be a malformed OTC BGP update attribute typically 4-bytes but in this case was 1024 on the prefix 2402:2de0::/32, our route server software reflected this back to peers as expected and routers tore down their session due to it. The permanent fix for this is upgrading bird the BGP software on the route servers to not propagate these malformed attributes.
- resolved Oct 08, 2025, 04:05 AM UTC
This incident is resolved for now. A new notice will come out for route server maintenance to resolve this permanently by adding RFC 9234 role capability.