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 7 in the last 90 days.

Source: status.catalystcloud.nz

49incidents recorded
21last 12 months
7last 90 days
8 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
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 (1%)
September 202623 of 720 (0%)
October 202600 of 508 (0%)

Incidents, newest first

Minor June 3, 2025 Experiencing issue with new instances 1h 15m Compute (nz-por-1), Network (nz-por-1)

Started Jun 03, 2025, 10:39 PM UTC· resolved Jun 03, 2025, 11:54 PM UTC

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

    We are currently investigating this issue.

  2. monitoring Jun 03, 2025, 11:15 PM UTC

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

  3. resolved Jun 03, 2025, 11:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 3, 2025 Issue affecting some customer servers in nz-hlz-1 51m Compute (nz-hlz-1)

Started Jun 03, 2025, 07:05 AM UTC· resolved Jun 03, 2025, 07:56 AM UTC

  1. identified Jun 03, 2025, 07:05 AM UTC

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

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

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

  4. resolved Jun 03, 2025, 07:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 10, 2025 Block storage service degraded in nz-hlz-1 –

Started Apr 10, 2025, 05:30 PM UTC· resolved Apr 10, 2025, 05:30 PM UTC

  1. resolved Apr 10, 2025, 09:42 PM UTC

    Between 05:43 and 05:57 a disk failure impacted the NVMe block storage service in the Hamilton region causing delayed or failed read and write requests. The impacted disk was removed from service by automated systems and latency recovered at 05:57.

Read the full incident report →

Minor March 15, 2025 Network service has degraded performance 3h 42m Network (nz-por-1)

Started Mar 15, 2025, 09:37 PM UTC· resolved Mar 16, 2025, 01:19 AM UTC

  1. investigating Mar 15, 2025, 09:37 PM UTC

    We have detected an issue with the creation of network resources in the nz-por-1 region. The issue may impact the creation of compute servers.

  2. identified Mar 15, 2025, 11:29 PM UTC

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

  3. monitoring Mar 16, 2025, 12:39 AM UTC

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

  4. resolved Mar 16, 2025, 01:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 14, 2025 NVME 2m Block storage (nz-por-1)

Started Feb 14, 2025, 01:30 AM UTC· resolved Feb 14, 2025, 01:32 AM UTC

  1. investigating Feb 14, 2025, 01:30 AM UTC

    NVME block storage experienced brief degradation beginning from approx 12:13 NZDT.

  2. resolved Feb 14, 2025, 01:32 AM UTC

    NVME performance issue resolved at approx. 12:15 NZDT.

Read the full incident report →

Minor January 11, 2025 Degraded performance for block storage in nz-por-1 5h 47m Block storage (nz-por-1)

Started Jan 11, 2025, 01:28 AM UTC· resolved Jan 11, 2025, 07:16 AM UTC

  1. investigating Jan 11, 2025, 01:28 AM UTC

    We are currently investigating this issue.

  2. monitoring Jan 11, 2025, 02:48 AM UTC

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

  3. resolved Jan 11, 2025, 07:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 4, 2024 Service API partial outage in the nz-por-1 region 3h 12m APIs (nz-por-1), Compute (nz-por-1), Block storage (nz-por-1), Network (nz-por-1) and 4 more

Started Dec 04, 2024, 11:18 PM UTC· resolved Dec 05, 2024, 02:31 AM UTC

  1. investigating Dec 04, 2024, 11:18 PM UTC

    We are currently investigating this issue.

  2. investigating Dec 04, 2024, 11:30 PM UTC

    The following API services are affected: * Compute * Networking * Block Storage * Load Balancers * Cloud Orchestration * Kubernetes cluster creations/updates/deletions (existing clusters are operating normally) Workloads are continuing to operate normally; however you may be unable to make any changes to workloads at this time. The following API services are operating normally: * Identity & Access Management * Object Storage

  3. monitoring Dec 05, 2024, 12:08 AM UTC

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

  4. resolved Dec 05, 2024, 02:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 8, 2024 Intermittent issues with block storage in nz-hlz-1 5h 13m Block storage (nz-hlz-1)

Started Nov 08, 2024, 06:17 PM UTC· resolved Nov 08, 2024, 11:31 PM UTC

  1. investigating Nov 08, 2024, 06:17 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 08, 2024, 06:18 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 08, 2024, 10:15 PM UTC

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

  4. resolved Nov 08, 2024, 11:31 PM UTC

    This incident has been resolved.

Read the full incident report →