- Level
- confirmed
- Worst impact
- Operational
- Components
- CockroachDB Advanced
What to do
Check whether you use CockroachDB Cloud CockroachDB Advanced. 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 8m it lasted.
Anything that failed between 2023-10-13 16:06 UTC and 2023-10-13 17:14 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
The Quay.io container registry is experiencing issues at the moment. Cockroach Cloud is monitoring updates - https://status.quay.io/incidents/3dq7w1tvs16f?u=bcn3g37v5rgb
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
Quay.io has indicated that the incident is resolved on their end.
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-5e7dac0c1a
Is CockroachDB Cloud still down?
No, this incident was resolved 2023-10-13 17:14 UTC. For CockroachDB Cloud's live state, see https://down.guide/providers/cockroachdb.
How long did it last?
1h 8m, from 2023-10-13 16:06 UTC to 2023-10-13 17:14 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.