Cockroach Labs incident
Degraded performance in one AWS us-east-1 availability zone
Cockroach Labs experienced a major incident on May 8, 2026 affecting CockroachDB Advanced, lasting 19h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring May 08, 2026, 02:13 AM UTC
AWS is experiencing elevated error rates and degraded performance in a single availability zone in the us-east-1 region. CockroachDB clusters in us-east-1 remain available, and we are monitoring the situation and taking corrective action as appropriate to ensure SQL availability of CockroachDB clusters in this region.
- monitoring May 08, 2026, 03:24 AM UTC
AWS's latest status update reports that they are continuing to work on the situation, and progress is slow. AWS has advised a next update time at 05:00 UTC. We continue to monitor the situation and take appropriate action to ensure uptime and availability for Cockroach DB clusters. We'll next update by about 05:00 UTC when we learn more from AWS.
- monitoring May 08, 2026, 08:25 AM UTC
AWS reports continued progress towards resolving the issue in the US-EAST-1 Region and is working towards full recovery. Affected services may continue to experience elevated error rates and latencies until recovery is complete. We continue to monitor the situation and take appropriate action to ensure uptime and availability for CockroachDB clusters. We'll provide another update as we learn more from AWS.
- resolved May 08, 2026, 09:53 PM UTC
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.