Catalyst Cloud Outage History

Catalyst Cloud is up right now

Catalyst Cloud had 15 outages in the last 2 years totaling 125h 0m of downtime — averaging 0.6 incidents per month.

There were 15 Catalyst Cloud outages since September 16, 2025 totaling 125h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.catalystcloud.nz

Major June 23, 2026

Object storage API outage

Detected by Pingoru
Jun 23, 2026, 12:02 AM UTC
Resolved
Jun 23, 2026, 12:23 AM UTC
Duration
21m
Affected: APIs (nz-hlz-1)APIs (nz-por-1)
Timeline · 4 updates
  1. identified Jun 23, 2026, 12:02 AM UTC

    The object storage API is currently unavailable in all regions. We have found the rootcause and are currently working on implementing a fix.

  2. identified Jun 23, 2026, 12:04 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jun 23, 2026, 12:13 AM UTC

    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.

  4. resolved Jun 23, 2026, 12:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 3, 2026

Emergency network maintenance

Detected by Pingoru
Jun 03, 2026, 05:01 AM UTC
Resolved
Jun 03, 2026, 05:41 AM UTC
Duration
40m
Affected: Network (nz-hlz-1)Network (nz-por-1)
Timeline · 4 updates
  1. identified Jun 03, 2026, 05:01 AM UTC

    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.

  2. identified Jun 03, 2026, 05:11 AM UTC

    The emergency maintenance in nz-por-1 is complete. nz-hlz-1 is still ongoing.

  3. monitoring Jun 03, 2026, 05:19 AM UTC

    The emergency maintenance in nz-hlz-1 is now complete. We are now monitoring for potential issues.

  4. resolved Jun 03, 2026, 05:41 AM UTC

    The emergency maintenance is complete.

Read the full incident report →

Major May 8, 2026

Porirua region outage

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
  1. investigating May 08, 2026, 06:05 PM UTC

    We are experiencing a major outage in the porirua region

  2. identified May 08, 2026, 06:28 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 08, 2026, 06:32 PM UTC

    We are continuing to work on a fix for this issue.

  4. 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.

  5. identified May 08, 2026, 08:12 PM UTC

    We are continuing to see degraded performance and are working through the solution

  6. 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.

  7. resolved May 09, 2026, 09:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Compute issue

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
  1. 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.

  2. resolved May 07, 2026, 04:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 15, 2026

Intermittent API failures in nz-por-1

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
  1. identified Apr 15, 2026, 04:12 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 15, 2026, 04:24 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 15, 2026, 05:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 13, 2026

Degraded compute and network api performance nz-por-1

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
  1. 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.

  2. identified Mar 13, 2026, 09:26 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 13, 2026, 09:31 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 13, 2026, 09:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 4, 2026

API issues in nz-por-1

Detected by Pingoru
Mar 04, 2026, 10:30 AM UTC
Resolved
Mar 04, 2026, 10:30 AM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Notice February 25, 2026

Storage latency issues for some instances in nz-hlz-1

Detected by Pingoru
Feb 25, 2026, 10:56 PM UTC
Resolved
Feb 25, 2026, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Major February 20, 2026

Network transit issues in nz-hlz-1

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
  1. 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.

  2. 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

  3. identified Feb 20, 2026, 08:05 PM UTC

    We are implementing a mitigation that will restore service.

  4. 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.

  5. 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.

  6. resolved Feb 20, 2026, 08:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 20, 2026

Unable to create new database instances in nz-hlz-1

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
  1. 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.

  2. 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 →

Minor February 5, 2026

Network issues in porirua

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
  1. investigating Feb 05, 2026, 02:00 AM UTC

    We are currently investigating this issue.

  2. identified Feb 05, 2026, 02:09 AM UTC

    One of our networking nodes has experienced a failure. We are currently migrating affected workloads.

  3. monitoring Feb 05, 2026, 02:12 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Feb 05, 2026, 02:34 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 05, 2026, 05:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 3, 2026

Block storage degraded in Hamilton

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
  1. investigating Feb 03, 2026, 04:26 PM UTC

    Block storage is degraded in hamilton due to hardware issues. We are working on a solution.

  2. resolved Feb 03, 2026, 05:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

CCKS cluster creation not completing

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
  1. 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.

  2. identified Jan 29, 2026, 01:06 AM UTC

    The issue has been identified and a fix is being implemented.

  3. 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.

  4. identified Jan 29, 2026, 08:40 PM UTC

    Fix has been rescheduled for Monday 2026-02-02.

  5. resolved Feb 02, 2026, 12:11 AM UTC

    This issue has been resolved.

Read the full incident report →

Notice January 27, 2026

Block storage porirua api issues

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
  1. 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

  2. monitoring Jan 27, 2026, 08:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 27, 2026, 08:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2025

Volume API errors in nz-por-1

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
  1. investigating Sep 16, 2025, 09:52 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 16, 2025, 10:21 PM UTC

    This incident has been resolved.

Read the full incident report →