Skip to main content
CockroachDB Cloud

Clusters on Azure may be experiencing instability

Degraded Lasted 1h · started · CockroachDB Cloud's page

Level
confirmed
Worst impact
Degraded
Down Index
17of 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 1h it lasted.

    Anything that failed between 2024-01-19 00:29 UTC and 2024-01-19 01:30 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

  1. investigating

    Some customers on Azure may be experiencing instability with their clusters, but all clusters remain up and functional at this time.

    provider

  2. resolved

    We have replaced the failing nodes and all clusters are stable now.

    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-ec0c2ddef2

Is CockroachDB Cloud still down?

No, this incident was resolved 2024-01-19 01:30 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.

How long did it last?

1h, from 2024-01-19 00:29 UTC to 2024-01-19 01:30 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.