- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 100
What to do
Check whether your product depends on CockroachDB Cloud. 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 3h 4m it lasted.
Anything that failed between 2025-07-02 17:42 UTC and 2025-07-02 20:46 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
- investigating
We are investigating cluster operations, including creating or editing clusters, that are taking longer than usual.
provider
- identified
We have identified the issue preventing cluster operations from proceeding, and we see that operations are moving forward. We will next update this incident by 16:00 EDT.
provider
- monitoring
We continue to see cluster operations succeeding, and will actively monitor to ensure the issue does not reoccur.
provider
- resolved
All cluster operations are succeeding normally at this time.
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-a655ad53c4
Is CockroachDB Cloud still down?
No, this incident was resolved 2025-07-02 20:46 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
3h 4m, from 2025-07-02 17:42 UTC to 2025-07-02 20:46 UTC, by the times CockroachDB Cloud posted.
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.