- Level
- confirmed
- Worst impact
- Degraded
- Components
- coreService
- Regions
- usa1, usa2s, usa3s, usa80s, usa220, usa240s, usa242s, usa244s, usa248s, usa250s, usa252s, usa254s, usa256s, usa258s, usa260s, usa312, usa314, usa316, usa318, usa320, usa322, usa324, usa326, usa328, usa330, usa332, usa334, usa336, usa338, usa340, usa342, usa344, usa346, usa348, usa350, usa352, usa354, usa356, usa358, usa360, usa366s, usa372, usa374, usa376, usa384, usa794, usa856, usa870s, usa872s, usa874s, usa876, usa948s, usa950s, usa960, usa994, usa1012, usa1016, usa1018, usa1022, usa1024, usa1026, usa1028, usa1030, usa1032, usa1034, usa1036s, usa1038, usa1074s, usa1076s, usa1078, usa1082, usa1088s, usa1092, usa1112, usa1122, usa1126, usa1148s, usa1176, usa1206s, usa1208s, usa1260s, usa1262s, usa1264s, usa1266s
- Down Index
- 36of 100
What to do
Check whether you use Salesforce coreService in usa1, usa2s, usa3s, usa80s. 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 37m it lasted.
Anything that failed between 2026-10-09 22:14 UTC and 2026-10-09 22:51 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 2
- impactradiusincrease
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
provider
- update
We’ve investigated and confirmed resolution of a third party performance degradation that impacted multiple Salesforce instances. Impacted customers may have experienced latency and errors. 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-d4b3a10163
Is Salesforce still down?
No, this incident was resolved 2026-10-09 22:51 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
37m, from 2026-10-09 22:14 UTC to 2026-10-09 22:51 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa1, usa2s, usa3s, usa80s.
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.