- Level
- confirmed
- Worst impact
- Degraded
- Components
- coreService
- Regions
- usa902s, usa9002, usa9004s, usa9006s, usa9008, usa9010s, usa9012s, usa9014, usa9016s, usa9018s, usa9020, usa9022s, usa9024s, usa9026, usa9028s, usa9402, usa9404s, usa9406s, usa9902, usa9904s, usa9918s
- Down Index
- 42of 100
What to do
Check whether you use Salesforce coreService in usa902s, usa9002, usa9004s, usa9006s. 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 6h 41m it lasted.
Anything that failed between 2026-10-20 04:04 UTC and 2026-10-20 10:45 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
- update
We're investigating a login issue where customers aren't receiving any outbound emails, including password reset emails and one-time passcodes (OTPs). This is preventing logins. We've identified a recent change to an email service component as the likely trigger. We're reverting the change to restore email delivery. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We restored email delivery by rolling back a recent change to an email service component. Customers now receive all new password reset and one-time passcode (OTP) emails. Some delayed emails remain queued, and we're flushing those queues so it delivers sooner. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.
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-a3c6bb034e
Is Salesforce still down?
No, this incident was resolved 2026-10-20 10:45 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
6h 41m, from 2026-10-20 04:04 UTC to 2026-10-20 10:45 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa902s, usa9002, usa9004s, usa9006s.
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.