CockroachDB Cloud outage, 1 March 2026

Cluster unavailability and degraded cluster operations in AWS me-central...

Started
Resolved
11 Mar 2026, 19:51 UTC (after 10 days)
Impact
Minor
Affected
CockroachDB Advanced

Last update from CockroachDB Cloud

Beginning March 1, 2026, a power outage caused by physical damage to AWS infrastructure affected multiple Availability Zones in the AWS me-central-1 (UAE) region, resulting in the unavailability of CockroachDB Cloud clusters in that region. A single Availability Zone in me-south-1 was also impacted, causing degraded performance for clusters in that region. While AWS has not yet fully restored power to all affected Availability Zones, Cockroach Labs has directly engaged all customers impacted by this incident, providing resolution guidance and hands-on remediation assistance, including cross-region data restoration where applicable. As remediation steps have been completed or provided to a...

11 Mar 2026, 19:51 UTC

Read the full incident on the official CockroachDB Cloud status page

Is CockroachDB Cloud down now?

This page is the record of one past incident. For the live status, see Is CockroachDB Cloud down right now? - it reads the official status page every 2 minutes.

Other CockroachDB Cloud incidents

  1. Stock out issues in GCP us-central1

  2. Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).

  3. Cloud Latency, Delays, Connection Issues

  4. Cluster connectivity and execution issues

  5. Cluster Creation Failure

  6. Unable to accept invites

  7. Degraded performance in one AWS us-east-1 availability zone

  8. Cloud Console Social Login Auth Unavailable

All recorded CockroachDB Cloud incidents