- Level
- confirmed
- Worst impact
- Major outage
- Components
- API (api.doppler.com), Dashboard (dashboard.doppler.com)
- Down Index
- 40of 100
What to do
Check whether you use Doppler API (api.doppler.com), Dashboard (dashboard.doppler.com). 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 59m it lasted.
Anything that failed between 2022-08-29 00:38 UTC and 2022-08-29 01:38 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 3
- investigating
We are currently investigating this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This issue was caused by a redis server running out of memory. We've increased the amount of memory allotted to this server. We'll also be setting up additional alerting on redis resource usage so that we can catch and prevent these issues in the future.
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-b5c8f224f0
Is Doppler still down?
No, this incident was resolved 2022-08-29 01:38 UTC. For Doppler's live state, see https://down.guide/doppler.
How long did it last?
59m, from 2022-08-29 00:38 UTC to 2022-08-29 01:38 UTC, by the times Doppler posted.
What was affected?
Doppler named API (api.doppler.com), Dashboard (dashboard.doppler.com).
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.