- Level
- confirmed
- Worst impact
- Major outage
- Components
- MarketingCloudCoreService, MarketingCloudLogin
- Regions
- db402025, db402026, db402028, db402029, db402030, db402031, db402032, db402033, db402034, db402038, db402039, db402040, db402041, db402042, db402043, db402045, db402048, db402049, db402050, db402051, db402052, db402053, db402055, db402057, db402058, db402059
- Down Index
- 58of 100
What to do
Check whether you use Salesforce MarketingCloudCoreService, MarketingCloudLogin in db402025, db402026, db402028, db402029. 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-20 13:33 UTC and 2026-10-20 14:10 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
Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the databases to maintain stability We apologize for the impact this incident may have had on your customers and their businesses. We’ill complete a full investigation to confirm the technical trigger and underlying cause, and to identify actions that prevent a recurrence.
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-8bc5ea69d4
Is Salesforce still down?
No, this incident was resolved 2026-10-20 14:10 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
37m, from 2026-10-20 13:33 UTC to 2026-10-20 14:10 UTC, by the times Salesforce posted.
What was affected?
Salesforce named MarketingCloudCoreService, MarketingCloudLogin in db402025, db402026, db402028, db402029.
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.