CockroachDB Cloud Status Page

May 8, 2026 · resolved May 8

All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do not expect any impact to CockroachDB clusters.

Mar 18, 2026 · resolved Mar 18

Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.

Mar 1, 2026 · resolved Mar 11

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 all directly impacted customers, we are resolving this incident from Cockroach Labs' perspective. Cluster creation in the affected regions remains restricted pending full AWS recovery. Customers with outstanding questions or concerns are encouraged to contact Cockroach Labs Support.

Feb 9, 2026 · resolved Feb 9

Standard and Basic clusters continue to function normally.

Feb 2, 2026 · resolved Feb 2

We have deployed and verified a fix. Advanced clusters should now create within normal time frames.