- Detected by Pingoru
- May 08, 2026, 06:05 PM UTC
- Resolved
- May 09, 2026, 09:20 AM UTC
- Duration
- 15h 15m
Affected: APIs (nz-por-1)Compute (nz-por-1)Block storage (nz-por-1)Object storage (nz-por-1)Network (nz-por-1)Load balancer (nz-por-1)Cloud orchestration (nz-por-1)Kubernetes (nz-por-1)Database service
Timeline · 7 updates
-
investigating May 08, 2026, 06:05 PM UTC
We are experiencing a major outage in the porirua region
-
identified May 08, 2026, 06:28 PM UTC
The issue has been identified and a fix is being implemented.
-
identified May 08, 2026, 06:32 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 08, 2026, 07:42 PM UTC
We are continuing to work on the fix for this issue. Network and block performance continue to be degraded. Other services are degraded as a flow-on effect from this.
-
identified May 08, 2026, 08:12 PM UTC
We are continuing to see degraded performance and are working through the solution
-
identified May 08, 2026, 08:25 PM UTC
We have a mitigation in place and expect no more performance degradation. Further updates will not be notified unless performance degrades again, please see http://catalystcloud.statuspage.io/ for the current status of the region.
-
resolved May 09, 2026, 09:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 04:03 AM UTC
- Resolved
- May 07, 2026, 04:56 AM UTC
- Duration
- 53m
Affected: Compute (nz-hlz-1)
Timeline · 2 updates
-
investigating May 07, 2026, 04:03 AM UTC
A compute issue affecting some instances has occurred in the nz-hlz-1 region and is under investigation.
-
resolved May 07, 2026, 04:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 04:12 AM UTC
- Resolved
- Apr 15, 2026, 05:24 AM UTC
- Duration
- 1h 12m
Affected: APIs (nz-por-1)
Timeline · 3 updates
-
identified Apr 15, 2026, 04:12 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 15, 2026, 04:24 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 15, 2026, 05:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 04:40 AM UTC
- Resolved
- Mar 13, 2026, 09:51 AM UTC
- Duration
- 5h 10m
Affected: Compute (nz-por-1)Network (nz-por-1)
Timeline · 4 updates
-
investigating Mar 13, 2026, 04:40 AM UTC
Instance creation is inconsistently slow. We are investigating the root cause. Retrying instance creation will normally work.
-
identified Mar 13, 2026, 09:26 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 13, 2026, 09:31 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 13, 2026, 09:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 10:30 AM UTC
- Resolved
- Mar 04, 2026, 10:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 04, 2026, 10:34 AM UTC
Some of our APIs in the nz-por-1 region were suffering from degraded performance and, occasionally, failed creation requests. This issue has now been resolved, and all APIs are now available again.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 10:56 PM UTC
- Resolved
- Feb 25, 2026, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 25, 2026, 10:56 PM UTC
One of our compute hypervisors in the nz-hlz-1 region suffered from a networking issue causing higher than usual latency for block storage access for instances hosted on that hypervisor. The issue has now been fixed, and all affected instances should now have performance restored.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 07:59 PM UTC
- Resolved
- Feb 20, 2026, 08:50 PM UTC
- Duration
- 50m
Affected: Network (nz-hlz-1)
Timeline · 6 updates
-
investigating Feb 20, 2026, 07:59 PM UTC
We are experiencing network transit issues across IPv4 in the nz-hlz-1 region. IPv6 is unaffected. We are currently investigating the issue.
-
identified Feb 20, 2026, 08:04 PM UTC
Magic Transit, one of our transit providers, is recovering from an outage. For more information: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt
-
identified Feb 20, 2026, 08:05 PM UTC
We are implementing a mitigation that will restore service.
-
monitoring Feb 20, 2026, 08:23 PM UTC
Some service has been restored. We are still working on the mitigation for all of our networks.
-
monitoring Feb 20, 2026, 08:30 PM UTC
Mitigations have now been implemented, and network transit has been restored. We are now monitoring for any further issues.
-
resolved Feb 20, 2026, 08:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 07:50 PM UTC
- Resolved
- Feb 20, 2026, 08:47 PM UTC
- Duration
- 56m
Affected: Database service
Timeline · 2 updates
-
investigating Feb 20, 2026, 07:50 PM UTC
Our automated testing has alerted to us that new database instances cannot currently be created in the nz-hlz-1 region. Existing database instances appear to be unaffected.
-
resolved Feb 20, 2026, 08:47 PM UTC
New database instances can now be created in the nz-hlz-1 region.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 02:00 AM UTC
- Resolved
- Feb 05, 2026, 05:04 AM UTC
- Duration
- 3h 4m
Affected: Network (nz-por-1)
Timeline · 5 updates
-
investigating Feb 05, 2026, 02:00 AM UTC
We are currently investigating this issue.
-
identified Feb 05, 2026, 02:09 AM UTC
One of our networking nodes has experienced a failure. We are currently migrating affected workloads.
-
monitoring Feb 05, 2026, 02:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Feb 05, 2026, 02:34 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 05, 2026, 05:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 04:26 PM UTC
- Resolved
- Feb 03, 2026, 05:07 PM UTC
- Duration
- 41m
Affected: Block storage (nz-hlz-1)
Timeline · 2 updates
-
investigating Feb 03, 2026, 04:26 PM UTC
Block storage is degraded in hamilton due to hardware issues. We are working on a solution.
-
resolved Feb 03, 2026, 05:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 01:06 AM UTC
- Resolved
- Feb 02, 2026, 12:11 AM UTC
- Duration
- 3d 23h
Affected: Kubernetes (nz-hlz-1)Kubernetes (nz-por-1)
Timeline · 5 updates
-
investigating Jan 29, 2026, 01:06 AM UTC
We are aware of an issue that is affecting newly created CCKS clusters completing their creation phase. This issue may be worked around by providing the label `kube_dashboard_enabled=false` on creation. For more details on labels see https://docs.catalystcloud.nz/kubernetes/appendix.html#k8s-cluster-labels We are working on a resolution to this and will update this statuspage message when the problem is resolved. This issue is not expected to impact running clusters.
-
identified Jan 29, 2026, 01:06 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jan 29, 2026, 03:31 AM UTC
A fix has been tested and we expect to deploy this for customers on Friday 2026-01-30. Until then, providing label `kube_dashboard_enabled=false` during cluster creation continues to be the recommended workaround.
-
identified Jan 29, 2026, 08:40 PM UTC
Fix has been rescheduled for Monday 2026-02-02.
-
resolved Feb 02, 2026, 12:11 AM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 08:32 PM UTC
- Resolved
- Jan 27, 2026, 08:49 PM UTC
- Duration
- 16m
Affected: Block storage (nz-por-1)
Timeline · 3 updates
-
investigating Jan 27, 2026, 08:32 PM UTC
We are experiencing api issues with block storage in porirua, unrelated to the current maintainance. Please see https://catalystcloud.statuspage.io/ for updates
-
monitoring Jan 27, 2026, 08:41 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 27, 2026, 08:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2025, 09:52 PM UTC
- Resolved
- Sep 16, 2025, 10:21 PM UTC
- Duration
- 29m
Affected: APIs (nz-por-1)Block storage (nz-por-1)
Timeline · 2 updates
-
investigating Sep 16, 2025, 09:52 PM UTC
We are currently investigating this issue.
-
resolved Sep 16, 2025, 10:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2025, 07:27 AM UTC
- Resolved
- Jun 16, 2025, 08:14 AM UTC
- Duration
- 47m
Affected: Compute (nz-por-1)
Timeline · 3 updates
-
investigating Jun 16, 2025, 07:27 AM UTC
An issue is being investigated in the nz-por-1 region impacting a small number of compute instances. Updates will be posted soon.
-
investigating Jun 16, 2025, 07:51 AM UTC
One of our hypervisors in the nz-por-1 region has crashed due to a hardware issue. We are currently migrating workloads off the failed hypervisor.
-
resolved Jun 16, 2025, 08:14 AM UTC
All affected instances have been migrated and restarted.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 11:02 PM UTC
- Resolved
- Jun 13, 2025, 02:04 AM UTC
- Duration
- 3h 1m
Affected: Kubernetes (nz-hlz-1)Kubernetes (nz-por-1)
Timeline · 2 updates
-
identified Jun 12, 2025, 11:02 PM UTC
We have identified an issue with initial creation of Kubernetes clusters where these are not progressing to completion. This issue appears to relate to an external provider and we expect clusters to progress once the access is resolved. Upgrade actions of existing clusters will also stall, but running clusters are otherwise not affected and can scale and run as normal.
-
resolved Jun 13, 2025, 02:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 03:40 PM UTC
- Resolved
- Jun 10, 2025, 04:41 PM UTC
- Duration
- 1h
Affected: Block storage (nz-hlz-1)Network (nz-hlz-1)
Timeline · 2 updates
-
investigating Jun 10, 2025, 04:39 PM UTC
A small number of instances have been affected by a network performance reduction in HLZ beginning from approx 0340 NZST.
-
resolved Jun 10, 2025, 04:41 PM UTC
Full performance was restored at approx 0410 NZST.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 10:39 PM UTC
- Resolved
- Jun 03, 2025, 11:54 PM UTC
- Duration
- 1h 15m
Affected: Compute (nz-por-1)Network (nz-por-1)
Timeline · 3 updates
-
investigating Jun 03, 2025, 10:39 PM UTC
We are currently investigating this issue.
-
monitoring Jun 03, 2025, 11:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 03, 2025, 11:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 07:05 AM UTC
- Resolved
- Jun 03, 2025, 07:56 AM UTC
- Duration
- 51m
Affected: Compute (nz-hlz-1)
Timeline · 4 updates
-
identified Jun 03, 2025, 07:05 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 03, 2025, 07:11 AM UTC
A compute hypervisor has crashed, some customer virtual machines are impacted. We are currently migrating customer workloads.
-
monitoring Jun 03, 2025, 07:35 AM UTC
The virtual machines have all been migrated and are now be running. We are keeping an eye on things but expect no further issues.
-
resolved Jun 03, 2025, 07:56 AM UTC
This incident has been resolved.
Read the full incident report →
