- Level
- confirmed
- Worst impact
- Degraded
- Components
- CockroachDB Advanced
- Regions
- us, us-east-1
- Down Index
- 29of 100
What to do
Check whether you use CockroachDB Cloud CockroachDB Advanced in us, us-east-1. 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 5h 44m it lasted.
Anything that failed between 2024-02-16 16:04 UTC and 2024-02-16 21: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 3
- monitoring
We are currently monitoring an incident with AWS firehose creation in `us-east-1` that is causing cluster creation in `us-eastt-1` to take longer than normal. There is no impact to existing clusters. Our engineers are monitoring the situation.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
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-85c703fa2b
Is CockroachDB Cloud still down?
No, this incident was resolved 2024-02-16 21:48 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.
How long did it last?
5h 44m, from 2024-02-16 16:04 UTC to 2024-02-16 21:48 UTC, by the times CockroachDB Cloud posted.
What was affected?
CockroachDB Cloud named CockroachDB Advanced in us, us-east-1.
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.