- Level
- confirmed
- Worst impact
- Degraded
- Components
- Agentforce, coreService
- Regions
- jpn2s, jpn4s, jpn6s, jpn8s, jpn10s, jpn12s, jpn18s, jpn20s, jpn22s, jpn24s, jpn28s, jpn132, jpn134, jpn136, jpn138, jpn140, jpn142, jpn144, jpn146, jpn150, jpn188
- Down Index
- 39of 100
What to do
Check whether you use Salesforce Agentforce, coreService in jpn2s, jpn4s, jpn6s, jpn8s. 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 42m it lasted.
Anything that failed between 2026-10-21 00:25 UTC and 2026-10-21 02: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 3
- update
We're aware of an issue impacting Agentforce Coworker. A subset of customers may experience intermittent request failures, and conversations may stop partway through an answer without an error message. We engaged the third-party service provider, and we're seeing error rates decrease. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- starttimerevision
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
provider
- update
Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services. 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-be59c6792e
Is Salesforce still down?
No, this incident was resolved 2026-10-21 02:07 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
1h 42m, from 2026-10-21 00:25 UTC to 2026-10-21 02:07 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Agentforce, coreService in jpn2s, jpn4s, jpn6s, jpn8s.
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.