Changes / CockroachDB / Degraded performance in one AWS us-east-1 availability zone
CockroachDB: Major incident: Degraded performance in one AWS us-east-1 availability zone
Summary
CockroachDB Advanced reported a major degradation linked to elevated AWS error rates and degraded performance in one us-east-1 availability zone; clusters remained available. The incident ran from 2026-05-08 02:13 UTC to 2026-05-08 21:53 UTC (19 h 40 min), when all clusters in the affected zone were restored to a fully operational state.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 94%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Degraded performance in one AWS us-east-1 availability zone
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-08 02:13 UTC
Before: not present
After: 2026-05-08 21:53 UTC
Before: not present
After: CockroachDB Advanced
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Degraded performance in one AWS us-east-1 availability zone (this change) CockroachDB Advanced reported a major degradation linked to elevated AWS error rates and degraded performance in one us-east-1 availability zone; clusters remained available. The incident ran from 2026-05-08 02:13 UTC to 2026-05-08 21:53 UTC (19 h 40 min), when all clusters in the affected zone were restored to a fully operational state. | Major incident |
All CockroachDB changes → · CockroachDB profile · Markdown · JSON