- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 5m it lasted.
Anything that failed between 2024-10-24 19:00 UTC and 2024-10-24 21:05 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 3
- identified
We are aware of an AWS incident that is preventing successful completion of Advanced cluster creation and region addition. Once the cloud provider has resolved their incident, we will ensure clusters create successfully.
provider
- identified
We are continuing to monitor the upstream incident.
provider
- resolved
The upstream incident has been resolved, and we have confirmed that cluster creation is working normally.
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-9c739c2af5
Is CockroachDB Cloud still down?
No, this incident was resolved 2024-10-24 21:05 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
2h 5m, from 2024-10-24 19:00 UTC to 2024-10-24 21:05 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.