- Level
- confirmed
- Worst impact
- Degraded
- Components
- AutomationStudio
- Regions
- db19, db26, db27, db32, db33, db38, db49, db400, db408, db409, db411, db412, db413, db414, db415, db417, db418, db419, db421, db422, db425, db427, db428, db429, db430, db431, db432, db434, db435, db437, db439, db440, db441, db442, db443, db444, db445, db446, db447, db449, db452, db453, db455, db457, db458, db459, db460, db461, db462, db463, db465, db466, db467, db468, db469, db470, db471
- Down Index
- 43of 100
What to do
Check whether you use Salesforce AutomationStudio in db19, db26, db27, db32. 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 1d 17h it lasted.
Anything that failed between 2026-10-03 16:14 UTC and 2026-10-05 10:07 UTC may need a replay.Subscribe to Salesforce's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Salesforce
No updates posted.
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-978606a7ae
Is Salesforce still down?
No, this incident was resolved 2026-10-05 10:07 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
1d 17h, from 2026-10-03 16:14 UTC to 2026-10-05 10:07 UTC, by the times Salesforce posted.
What was affected?
Salesforce named AutomationStudio in db19, db26, db27, db32.
What caused it?
Salesforce hasn't published a root cause. If it does, it shows here.
Where does this come from?
Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.