- Level
- confirmed
- Worst impact
- Major outage
- Components
- coreService
- Regions
- usa1198s
- Down Index
- 47of 100
What to do
Check whether you use Salesforce coreService in usa1198s. 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 17m it lasted.
Anything that failed between 2026-10-14 18:46 UTC and 2026-10-14 19:03 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.
Root cause
We’re investigating the cause of the issue.Read the postmortem
Updates from Salesforce 1
- investigatingcauseofissue
We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
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-24702a2010
Is Salesforce still down?
No, this incident was resolved 2026-10-14 19:03 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
17m, from 2026-10-14 18:46 UTC to 2026-10-14 19:03 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa1198s.
What caused it?
Salesforce wrote: "We’re investigating the cause of the issue." The postmortem: https://status.salesforce.com/incidents/20004485
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.