Skip to main content
CockroachDB Cloud

Serverless Cluster Resource Limit Throttling

Partial outage Lasted 3h 39m · started · CockroachDB Cloud's page

Level
confirmed
Worst impact
Partial outage
Regions
ap-south-1, eu, eu-west-1
Down Index
42of 100

What to do

  • Check whether you use CockroachDB Cloud in ap-south-1, eu, eu-west-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 3h 39m it lasted.

    Anything that failed between 2023-08-02 16:05 UTC and 2023-08-02 19:44 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 4

  1. investigating

    Some Serverless clusters that have hit their resource limits are still being throttled even after limits have been increased. Currently only AWS eu-west-1 and ap-south-1 host clusters are impacted

    provider

  2. investigating

    Some Serverless clusters that have hit their resource limits are still being throttled even after limits have been increased.

    provider

  3. identified

    The scope of the impact has been limited to serverless clusters running AWS eu-west-1 and AWS ap-south-1. Clusters that have hit their resource limits will be throttled despite having their limits increased. One of two issues identified has been mitigated.

    provider

  4. resolved

    This issue has now been resolved. Users with clusters that were previously throttled will now see their changes to resource limits reflected.

    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-43f1d55d01

Is CockroachDB Cloud still down?

No, this incident was resolved 2023-08-02 19:44 UTC. For CockroachDB Cloud's live state, see https://down.guide/cockroachdb.

How long did it last?

3h 39m, from 2023-08-02 16:05 UTC to 2023-08-02 19:44 UTC, by the times CockroachDB Cloud posted.

What was affected?

CockroachDB Cloud named in ap-south-1, eu, eu-west-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.