- Level
- confirmed
- Worst impact
- Degraded
- Components
- Splunk
- Down Index
- 19of 100
What to do
Check whether you use Doppler Splunk. 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 47m it lasted.
Anything that failed between 2024-05-31 18:04 UTC and 2024-05-31 19:51 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
- identified
Activity Logs stopped publishing to Splunk as of May 30th at 19:55 UTC. The issue has been identified and a fix is in progress. After the issue has been resolved and the connections reconnected, missed activity logs will be republished.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- resolved
A fix has been deployed and we are monitoring reconnections. We will backfill missed Activity Logs as needed after workplaces reconnect Splunk.
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-60b70565c7
Is Doppler still down?
No, this incident was resolved 2024-05-31 19:51 UTC. For Doppler's live state, see https://down.guide/providers/doppler.
How long did it last?
1h 47m, from 2024-05-31 18:04 UTC to 2024-05-31 19:51 UTC, by the times Doppler posted.
What was affected?
Doppler named Splunk.
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.