Catalyst Cloud Outage History

Catalyst Cloud is up right now

Pingoru has recorded 49 incidents for Catalyst Cloud: 21 in the last 12 months and 5 in the last 90 days.

Source: status.catalystcloud.nz

49incidents recorded
21last 12 months
5last 90 days
8 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Catalyst Cloud in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 2026216 of 744 (2%)
June 202621 of 720 (0%)
July 2026227 of 744 (4%)
August 202634 of 744 (0%)
September 202623 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 44 (0%)

Incidents, newest first

Major September 30, 2026 issues scheduling new instances in nz-por-1 1h 8m Compute (nz-por-1)

Started Sep 30, 2026, 03:23 AM UTC· resolved Sep 30, 2026, 04:31 AM UTC

  1. investigating Sep 30, 2026, 03:23 AM UTC

    We are currently investigating this issue.

  2. monitoring Sep 30, 2026, 03:53 AM UTC

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

  3. resolved Sep 30, 2026, 04:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 30, 2026 Packet loss in nz-por-1 region 1h 43m Network (nz-por-1)

Started Sep 30, 2026, 12:45 AM UTC· resolved Sep 30, 2026, 02:29 AM UTC

  1. investigating Sep 30, 2026, 12:45 AM UTC

    We're seeing an increase in packet loss in the Porirua region.

  2. identified Sep 30, 2026, 12:57 AM UTC

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

  3. monitoring Sep 30, 2026, 01:10 AM UTC

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

  4. resolved Sep 30, 2026, 02:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 19, 2026 OpenStack APIs not accessible from some domains 7m APIs (nz-hlz-1), APIs (nz-por-1)

Started Aug 19, 2026, 02:37 AM UTC· resolved Aug 19, 2026, 02:45 AM UTC

  1. identified Aug 19, 2026, 02:37 AM UTC

    `api.nz-hlz-1.catalystcloud.nz` and `api.nz-por-1.catalystcloud.nz` are currently inaccessible. This will only affect any customers using these endpoints specifically; the standard endpoints most clients currently interact with, located at `api.nz-hlz-1.catalystcloud.io` and `api.nz-por-1.catalystcloud.io` are still working correctly. We are working on a solution to this issue.

  2. monitoring Aug 19, 2026, 02:42 AM UTC

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

  3. resolved Aug 19, 2026, 02:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 17, 2026 Network interface issue with GPU hypervisor 3h 8m Compute (nz-por-1)

Started Aug 17, 2026, 03:16 AM UTC· resolved Aug 17, 2026, 06:25 AM UTC

  1. investigating Aug 17, 2026, 03:16 AM UTC

    We have detected an issue with the networking on one of our GPU hypervisors and performing maintenance on the hypervisor.

  2. monitoring Aug 17, 2026, 03:49 AM UTC

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

  3. resolved Aug 17, 2026, 06:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2026 Block storage performance degradation in nz-hlz-1 30m Block storage (nz-hlz-1)

Started Aug 12, 2026, 07:53 PM UTC· resolved Aug 12, 2026, 08:23 PM UTC

  1. investigating Aug 12, 2026, 07:53 PM UTC

    We are currently investigating this issue.

  2. identified Aug 12, 2026, 08:01 PM UTC

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

  3. monitoring Aug 12, 2026, 08:07 PM UTC

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

  4. resolved Aug 12, 2026, 08:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2026 C3-GPU networking issues 19h 54m Compute (nz-por-1)

Started Jul 30, 2026, 12:21 AM UTC· resolved Jul 30, 2026, 08:16 PM UTC

  1. investigating Jul 30, 2026, 12:21 AM UTC

    We are seeing issues with connectivity to C3-GPU instances and are investigating.

  2. identified Jul 30, 2026, 01:50 AM UTC

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

  3. monitoring Jul 30, 2026, 01:55 AM UTC

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

  4. resolved Jul 30, 2026, 08:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 27, 2026 Degraded networking performance in nz-por-1 7h 21m Network (nz-por-1)

Started Jul 27, 2026, 09:57 PM UTC· resolved Jul 28, 2026, 05:18 AM UTC

  1. investigating Jul 27, 2026, 09:57 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 27, 2026, 10:18 PM UTC

    We are investigating a potential cause.

  3. monitoring Jul 27, 2026, 10:57 PM UTC

    The immediate issue has been resolved but we will continue to monitor the situation.

  4. resolved Jul 28, 2026, 05:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2026 Object storage API outage 21m APIs (nz-hlz-1), APIs (nz-por-1)

Started Jun 23, 2026, 12:02 AM UTC· resolved Jun 23, 2026, 12:23 AM UTC

  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 40m Network (nz-hlz-1), Network (nz-por-1)

Started Jun 03, 2026, 05:01 AM UTC· resolved Jun 03, 2026, 05:41 AM UTC

  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 15h 15m APIs (nz-por-1), Compute (nz-por-1), Block storage (nz-por-1), Object storage (nz-por-1) and 5 more

Started May 08, 2026, 06:05 PM UTC· resolved May 09, 2026, 09:20 AM UTC

  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 53m Compute (nz-hlz-1)

Started May 07, 2026, 04:03 AM UTC· resolved May 07, 2026, 04:56 AM UTC

  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 1h 12m APIs (nz-por-1)

Started Apr 15, 2026, 04:12 AM UTC· resolved Apr 15, 2026, 05:24 AM UTC

  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 5h 10m Compute (nz-por-1), Network (nz-por-1)

Started Mar 13, 2026, 04:40 AM UTC· resolved Mar 13, 2026, 09:51 AM UTC

  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 –

Started Mar 04, 2026, 10:30 AM UTC· resolved Mar 04, 2026, 10:30 AM UTC

  1. resolved Mar 04, 2026, 10:30 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 –

Started Feb 25, 2026, 10:00 PM UTC· resolved Feb 25, 2026, 10:00 PM UTC

  1. resolved Feb 25, 2026, 10:00 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 50m Network (nz-hlz-1)

Started Feb 20, 2026, 07:59 PM UTC· resolved Feb 20, 2026, 08:50 PM UTC

  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 56m Database service

Started Feb 20, 2026, 07:50 PM UTC· resolved Feb 20, 2026, 08:47 PM UTC

  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 3h 4m Network (nz-por-1)

Started Feb 05, 2026, 02:00 AM UTC· resolved Feb 05, 2026, 05:04 AM UTC

  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 41m Block storage (nz-hlz-1)

Started Feb 03, 2026, 04:26 PM UTC· resolved Feb 03, 2026, 05:07 PM UTC

  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 3d 23h Kubernetes (nz-hlz-1), Kubernetes (nz-por-1)

Started Jan 29, 2026, 01:06 AM UTC· resolved Feb 02, 2026, 12:11 AM UTC

  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 16m Block storage (nz-por-1)

Started Jan 27, 2026, 08:32 PM UTC· resolved Jan 27, 2026, 08:49 PM UTC

  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 29m APIs (nz-por-1), Block storage (nz-por-1)

Started Sep 16, 2025, 09:52 PM UTC· resolved Sep 16, 2025, 10:21 PM UTC

  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 →

Major June 16, 2025 Compute issue in POR 47m Compute (nz-por-1)

Started Jun 16, 2025, 07:27 AM UTC· resolved Jun 16, 2025, 08:14 AM UTC

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

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

  3. resolved Jun 16, 2025, 08:14 AM UTC

    All affected instances have been migrated and restarted.

Read the full incident report →

Major June 12, 2025 CCKS Kubernetes Cluster: creation and upgrades 3h 1m Kubernetes (nz-hlz-1), Kubernetes (nz-por-1)

Started Jun 12, 2025, 11:02 PM UTC· resolved Jun 13, 2025, 02:04 AM UTC

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

  2. resolved Jun 13, 2025, 02:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2025 Network degregation in HLZ 1h Block storage (nz-hlz-1), Network (nz-hlz-1)

Started Jun 10, 2025, 03:40 PM UTC· resolved Jun 10, 2025, 04:41 PM UTC

  1. investigating Jun 10, 2025, 03:40 PM UTC

    A small number of instances have been affected by a network performance reduction in HLZ beginning from approx 0340 NZST.

  2. resolved Jun 10, 2025, 04:41 PM UTC

    Full performance was restored at approx 0410 NZST.

Read the full incident report →