- Level
- confirmed
- Worst impact
- Partial outage
- Components
- CockroachDB Advanced
- Regions
- us, us-east-1
- Down Index
- 41of 100
What to do
Check whether you use CockroachDB Cloud CockroachDB Advanced in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 19h 40m it lasted.
Anything that failed between 2026-05-08 02:13 UTC and 2026-05-08 21:53 UTC may need a replay.Subscribe to CockroachDB Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cockroachdb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from CockroachDB Cloud 4
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bc66862314
Is CockroachDB Cloud still down?
No, this incident was resolved 2026-05-08 21:53 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
19h 40m, from 2026-05-08 02:13 UTC to 2026-05-08 21:53 UTC, by the times CockroachDB Cloud posted.
What was affected?
CockroachDB Cloud named CockroachDB Advanced in us, us-east-1.
What caused it?
CockroachDB Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
CockroachDB Cloud's official status page, https://status.cockroachlabs.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.