- Level
- confirmed
- Worst impact
- Major outage
- Components
- coreService
- Regions
- usa700
- Down Index
- 52of 100
What to do
Check whether you use Salesforce coreService in usa700. 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 3h 25m it lasted.
Anything that failed between 2026-10-23 01:25 UTC and 2026-10-23 04:50 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
We resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again. 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-245d7eac71
Is Salesforce still down?
No, this incident was resolved 2026-10-23 04:50 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
3h 25m, from 2026-10-23 01:25 UTC to 2026-10-23 04:50 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa700.
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.