Catalyst Cloud Outage History

Catalyst Cloud is up right now

Catalyst Cloud had 33 outages in the last 2 years totaling 20h 5m of downtime — averaging 1.4 incidents per month.

There were 33 Catalyst Cloud outages since November 8, 2024 totaling 20h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.catalystcloud.nz

Minor June 3, 2025

Experiencing issue with new instances

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

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

Detected by Pingoru
Apr 10, 2025, 05:30 PM UTC
Resolved
Apr 10, 2025, 05:30 PM UTC
Duration
—
Timeline · 1 update
  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

Detected by Pingoru
Mar 15, 2025, 09:37 PM UTC
Resolved
Mar 16, 2025, 01:19 AM UTC
Duration
3h 42m
Affected: Network (nz-por-1)
Timeline · 4 updates
  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

Detected by Pingoru
Feb 14, 2025, 01:30 AM UTC
Resolved
Feb 14, 2025, 01:32 AM UTC
Duration
2m
Affected: Block storage (nz-por-1)
Timeline · 2 updates
  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

Detected by Pingoru
Jan 11, 2025, 01:28 AM UTC
Resolved
Jan 11, 2025, 07:16 AM UTC
Duration
5h 47m
Affected: Block storage (nz-por-1)
Timeline · 3 updates
  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

Detected by Pingoru
Dec 04, 2024, 11:18 PM UTC
Resolved
Dec 05, 2024, 02:31 AM UTC
Duration
3h 12m
Affected: APIs (nz-por-1)Compute (nz-por-1)Block 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 · 4 updates
  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

Detected by Pingoru
Nov 08, 2024, 06:17 PM UTC
Resolved
Nov 08, 2024, 11:31 PM UTC
Duration
5h 13m
Affected: Block storage (nz-hlz-1)
Timeline · 4 updates
  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 →