- Level
- confirmed
- Worst impact
- Major outage
- Components
- Agentforce
- Regions
- can2s, can4s, can6s, can8s, can20s, can26, can28, can34, can36, can38, can40, can42, can44, can46, can48, can50, can52, can54, can56, can70s, can80, can86s, can96, can98, usa8s, usa20s, usa22s, usa26, usa28s, usa30s, usa32s, usa34, usa36, usa60s, usa62s, usa202s, usa224s, usa226, usa228, usa230, usa232, usa234, usa236, usa238, usa262s, usa268s, usa270s, usa272, usa274, usa276, usa278, usa280, usa282, usa286, usa288, usa290, usa292, usa294, usa296, usa300, usa302, usa304, usa364, usa408, usa410, usa412, usa414, usa416, usa418, usa420, usa422, usa424, usa426, usa428, usa430, usa432s, usa434s, usa436, usa438, usa440, usa442, usa444, usa446s, usa448s, usa450, usa452, usa454, usa456, usa460, usa462, usa464, usa466, usa468, usa470, usa472, usa474, usa476, usa478, usa480, usa488s, usa490s, usa494, usa496, usa534s, usa538, usa540s, usa542s, usa544, usa546, usa548, usa550, usa552, usa554, usa556, usa558, usa560, usa562, usa564, usa566, usa568, usa570, usa572, usa574, usa576, usa578, usa580, usa582, usa584, usa586, usa588, usa590, usa592, usa594, usa596, usa598, usa600, usa602, usa604, usa606, usa608, usa610, usa612, usa614, usa616, usa618, usa620, usa622, usa624, usa626, usa628, usa630, usa632, usa634, usa636, usa638, usa640, usa642, usa644, usa646, usa648, usa650, usa652, usa654s, usa656s, usa658s, usa660s, usa662s, usa664s, usa666s, usa668s, usa670s, usa672s, usa674, usa676, usa678, usa680, usa682, usa684, usa686, usa688, usa690, usa692, usa694, usa696, usa698, usa700, usa702, usa704, usa706, usa708, usa880s, usa882s, usa884s, usa886s, usa888s, usa890s, usa892s, usa894s, usa896s, usa898s, usa900s, usa902s, usa1056, usa1194s, usa1196s, usa1198s, usa1200s, usa1202s, usa1234s, usa1236s, usa1238s, usa1240s, usa1242s, usa1244s, usa1246s, usa1248s, usa1250s, usa1252s
- Down Index
- 61of 100
What to do
Check whether you use Salesforce Agentforce in can2s, can4s, can6s, can8s. 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 1h 50m it lasted.
Anything that failed between 2026-10-20 14:40 UTC and 2026-10-20 16:30 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 1
- update
During this time Agentforce Coworker may have been unresponsive for some customers. The issue was linked to reduced availability of a third-party service that Coworker relies on. That service has recovered, and Agentforce Coworker is now operating normally. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat 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-429414509e
Is Salesforce still down?
No, this incident was resolved 2026-10-20 16:30 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
1h 50m, from 2026-10-20 14:40 UTC to 2026-10-20 16:30 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Agentforce in can2s, can4s, can6s, can8s.
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.