- Level
- confirmed
- Worst impact
- Degraded
- Components
- API (api.doppler.com), Dashboard (dashboard.doppler.com)
- Down Index
- 20of 100
What to do
Check whether you use Doppler API (api.doppler.com), Dashboard (dashboard.doppler.com). Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 55m it lasted.
Anything that failed between 2024-10-30 22:10 UTC and 2024-10-31 00:05 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 5
- investigating
Certain users may be unable to fetch from personal configs.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
A fix has been identified and should be deployed soon.
provider
- investigating
Only users with access to personal configs via groups are affected. Users with direct access to personal configs are not affected.
provider
- resolved
This incident has been resolved.
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-d05fbb7012
Is Doppler still down?
No, this incident was resolved 2024-10-31 00:05 UTC. For Doppler's live state, see https://down.guide/providers/doppler.
How long did it last?
1h 55m, from 2024-10-30 22:10 UTC to 2024-10-31 00:05 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.