COCKROACHDB

🔴 AWS me-central-1 lost power, and CockroachDB's clusters are discovering they can't actually survive in the dark. AWS is playing electrician while your cluster operations contemplate the fragility of cloud infrastructure. Check back when the lights come back on. (Auto-resolved: no updates in 24h)

⏰ Mar 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Cluster operations may fail due to regional outage in AWS me-central-1 region

// Status page says

Mar 1 , 15:11 UTC Monitoring - A power outage at an AWS facility in the me-central-1 (Mid-East) region may cause failures or slower than usual progress on cluster operations. AWS is aware of the issue and is working to restore power. We are monitoring the situation, and will provide updates as we receive them from AWS.

🔗 Official status page (for the PR-approved version)

https://status.cockroachlabs.cloud/incidents/fhx8k1nh1kz7

Cockroachdb's Greatest Hits

🟢 COCKROACHDB Sep 01, 2026

🟠 Google Cloud's infrastructure threw a tantrum, leaving Cockroach Cloud customers in us-central-1 and asia-east-1 dealing with latency, delays, and connection issues. Turns out blaming 'the cloud' is literally accurate this time. Teams are 'fully engaged' which is corporate for 'sweating profusely.'. (Auto-resolved: no updates in 24h)

🟢 COCKROACHDB Mar 18, 2026

🔴 COCKROACHDB - Cloud Console Social Login Auth Unavailable. (Auto-resolved: no updates in 24h)

🟢 COCKROACHDB Mar 11, 2026

⚪ AWS me-central-1 had a very bad day when someone tripped over a power cable in the UAE data center, yeeting multiple availability zones offline. CockroachDB clusters in the region went full zombie mode while me-south-1 just limped along like it'd been hit by a truck. AWS is still picking up the pieces. (Auto-resolved: no updates in 24h)

🟢 COCKROACHDB Mar 02, 2026

🔴 Two availability zones collapsed in AWS me-central-1, leaving clusters completely offline. me-south-1 got the degraded experience special with single AZ failure. GCP and Azure laughing from the sidelines while customers frantically dust off disaster recovery plans written in 2019. (Auto-resolved: no updates in 24h)