- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 100
What to do
Check whether your product depends on CockroachDB Cloud. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 48m it lasted.
Anything that failed between 2024-11-19 16:48 UTC and 2024-11-19 18:36 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.
Root cause
The root cause of the issue was identified and resolved.Read the postmortem
Updates from CockroachDB Cloud 3
- investigating
We have received alerts indicating elevated error rates on isolated Standard and Basic clusters. The Engineering team is currently investigating the issue.
provider
- monitoring
The root cause of the issue was identified and resolved. Engineering is monitoring the situation.
provider
- resolved
The Engineering team has isolated and resolved the elevated error rate for all affected 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-760cdf7f37
Is CockroachDB Cloud still down?
No, this incident was resolved 2024-11-19 18:36 UTC. For CockroachDB Cloud's live state, see https://down.guide/providers/cockroachdb.
How long did it last?
1h 48m, from 2024-11-19 16:48 UTC to 2024-11-19 18:36 UTC, by the times CockroachDB Cloud posted.
What caused it?
CockroachDB Cloud wrote: "The root cause of the issue was identified and resolved." The postmortem: https://stspg.io/hjd04kyyzjh9
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.