Skip to main content
Doppler

API unavailable due to contention over database locking

Partial outage Lasted 0m · started · Doppler's page

Level
confirmed
Worst impact
Partial outage
Down Index
18of 100

What to do

  • Check whether your product depends on Doppler. 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 0m it lasted.

    Anything that failed between 2021-10-01 19:34 UTC and 2021-10-01 09:00 UTC may need a replay.
  • Subscribe to Doppler's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=doppler works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Doppler 1

  1. resolved

    Our API experienced an 11 minute outage due to database contention over locking our Workplace table. The issue resolved itself once the locks expired. We've refactored the affected component to achieve the desired result without locking. We'll be exploring a more holistic fix to prevent this issue from occurring in other components.

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

Is Doppler still down?

No, this incident was resolved 2021-10-01 09:00 UTC. For Doppler's live state, see https://down.guide/doppler.

How long did it last?

0m, from 2021-10-01 19:34 UTC to 2021-10-01 09:00 UTC, by the times Doppler posted.

What caused it?

Doppler hasn't published a root cause. If it does, it shows here.

Where does this come from?

Doppler's official status page, https://www.dopplerstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.