- Level
- confirmed
- Worst impact
- Degraded
- Components
- CockroachDB Advanced
- Down Index
- 23of 100
What to do
Check whether you use CockroachDB Cloud CockroachDB Advanced. 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 6h 42m it lasted.
Anything that failed between 2025-07-21 21:39 UTC and 2025-07-22 04:22 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 2
- identified
We are aware of an ongoing Incident with dependent service "Let's Encrypt": https://letsencrypt.status.io/, which may impact cluster creation and add region operations for CockroachDB Cloud Advanced clusters. We will update this status page with more information as it becomes available.
provider
- resolved
LetsEncrypt has indicated the issue has been mitigated. We have validated cluster creation behaviour is now returning to normal.
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-646c3c9e81
Is CockroachDB Cloud still down?
No, this incident was resolved 2025-07-22 04:22 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
6h 42m, from 2025-07-21 21:39 UTC to 2025-07-22 04:22 UTC, by the times CockroachDB Cloud posted.
What was affected?
CockroachDB Cloud named CockroachDB Advanced.
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.