- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 42m it lasted.
Anything that failed between 2023-11-14 21:53 UTC and 2023-11-14 23:35 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
- monitoring
The Quay.io container registry is experiencing issues at the moment. CockroachDB Cloud is monitoring updates - https://status.quay.io/
provider
- resolved
Cluster operations appear to once again be healthy. We will continue to monitor for subsequent events/impacts due to the ongoing Quay.io issue.
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-2c4b5cb88d
Is CockroachDB Cloud still down?
No, this incident was resolved 2023-11-14 23:35 UTC. For CockroachDB Cloud's live state, see https://down.guide/providers/cockroachdb.
How long did it last?
1h 42m, from 2023-11-14 21:53 UTC to 2023-11-14 23:35 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.