- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 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 2020-02-06 23:43 UTC and 2020-02-06 23:43 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
- resolved
We had a migration script that failed to run before the rest of our services deployed. This caused the newly deployed services to crash because the database was missing a column in a critical table. Our deployment orchestrator quickly detected the issue and reverted to the previous build. Total downtime was approximately 2 minutes. We plan to mitigate future failures by requiring our migrations to complete before rolling out our remaining services.
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-76b4d11750
Is Doppler still down?
No, this incident was resolved 2020-02-06 23:43 UTC. For Doppler's live state, see https://down.guide/doppler.
How long did it last?
0m, from 2020-02-06 23:43 UTC to 2020-02-06 23:43 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.