- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2024-06-17 14:48 UTC and 2024-06-17 14:48 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 1
- resolved
A cluster setting update resulted in higher than expected CPU activity, which caused increased latency and caused unavailability for a single Serverless cluster. The setting was rolled back to prevent further impact. The issue has been resolved. There should be no further availability impact.
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-58400dc8c5
Is CockroachDB Cloud still down?
No, this incident was resolved 2024-06-17 14:48 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
0m, from 2024-06-17 14:48 UTC to 2024-06-17 14:48 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.