- Level
- confirmed
- Worst impact
- Degraded
- Components
- coreService
- Regions
- usa1210
- Down Index
- 25of 100
What to do
Check whether you use Salesforce coreService in usa1210. 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 22m it lasted.
Anything that failed between 2026-10-15 07:07 UTC and 2026-10-15 07:29 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-8839e9e177
Is Salesforce still down?
No, this incident was resolved 2026-10-15 07:29 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
22m, from 2026-10-15 07:07 UTC to 2026-10-15 07:29 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa1210.
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.