- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
What to do
Check whether you use CockroachDB Cloud in us, us-east-1. 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 17h 24m it lasted.
Anything that failed between 2023-09-28 21:09 UTC and 2023-09-29 14:33 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've been advised of a networking issue in the AWS us-east-1 region that may affect cluster creation. We're currently waiting on an update from AWS for an estimated recovery time. https://health.aws.amazon.com/health/status
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-8f1f0354c8
Is CockroachDB Cloud still down?
No, this incident was resolved 2023-09-29 14:33 UTC. For CockroachDB Cloud's live state, see https://down.guide/providers/cockroachdb.
How long did it last?
17h 24m, from 2023-09-28 21:09 UTC to 2023-09-29 14:33 UTC, by the times CockroachDB Cloud posted.
What was affected?
CockroachDB Cloud named 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.