← Back to CockroachDB History
major✓ Resolved

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

CockroachDBFri, May 8, 2026, 02:13 AM
Status
resolved
Duration
19h 41m
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, May 8, 2026, 09:55 PM
This incident has been resolved.
monitoringFri, May 8, 2026, 08:25 AM
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.
monitoringFri, May 8, 2026, 03:24 AM
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.
monitoringFri, May 8, 2026, 02:13 AM
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.

📊 TECHNICAL DETAILS

Internal ID
6d7606f1-264f-4db9-93bf-f804bdd75467
External ID
wfg5h93wm72w
🕐 Started
Fri, May 8, 2026, 02:13 AM
🔄 Last Updated
Fri, May 8, 2026, 09:55 PM
✓ Resolved
Fri, May 8, 2026, 09:55 PM
MAJOR
Impact Level
19h 41m
Total Duration
3
Status Updates
Affected Components
CockroachDB Advanced
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed