Catalyst Cloud Outage History

Catalyst Cloud is up right now

There were 8 Catalyst Cloud outages since February 3, 2026 totaling 11h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.catalystcloud.nz

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 →

Looking to track Catalyst Cloud downtime and outages?

Pingoru polls Catalyst Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Catalyst Cloud reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Catalyst Cloud alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Catalyst Cloud for free

5 free monitors · No credit card required