Catalyst Cloud had 16 outages in the last 2 years totaling 132h 21m of downtime — averaging 0.7 incidents per month.
There were 16 Catalyst Cloud outages since September 16, 2025 totaling 132h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are investigating a potential cause.
The immediate issue has been resolved but we will continue to monitor the situation.
This incident has been resolved.
The object storage API is currently unavailable in all regions. We have found the rootcause and are currently working on implementing a fix.
We are continuing to work on a fix for this issue.
The object storage API in nz-hlz-1 is now working again. It was previously reported that the API in nz-por-1 was also unavailable, but it was unaffected and continued working throughout the outage period. We are now monitoring for any further issues.
This incident has been resolved.
We are currently performing emergency maintenance on the network services in both the nz-por-1 and nz-hlz-1 regions. Workloads may see temporary interruptions in connectivity until the maintenance is complete.
The emergency maintenance in nz-por-1 is complete. nz-hlz-1 is still ongoing.
The emergency maintenance in nz-hlz-1 is now complete. We are now monitoring for potential issues.
The emergency maintenance is complete.
We are experiencing a major outage in the porirua region
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
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.
We are continuing to see degraded performance and are working through the solution
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.
This incident has been resolved.
A compute issue affecting some instances has occurred in the nz-hlz-1 region and is under investigation.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Instance creation is inconsistently slow. We are investigating the root cause. Retrying instance creation will normally work.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
We are experiencing network transit issues across IPv4 in the nz-hlz-1 region. IPv6 is unaffected. We are currently investigating the issue.
Magic Transit, one of our transit providers, is recovering from an outage. For more information: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt
We are implementing a mitigation that will restore service.
Some service has been restored. We are still working on the mitigation for all of our networks.
Mitigations have now been implemented, and network transit has been restored. We are now monitoring for any further issues.
This incident has been resolved.
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.
New database instances can now be created in the nz-hlz-1 region.
We are currently investigating this issue.
One of our networking nodes has experienced a failure. We are currently migrating affected workloads.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Block storage is degraded in hamilton due to hardware issues. We are working on a solution.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
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.
Fix has been rescheduled for Monday 2026-02-02.
This issue has been resolved.
We are experiencing api issues with block storage in porirua, unrelated to the current maintainance. Please see https://catalystcloud.statuspage.io/ for updates
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.