- Level
- confirmed
- Worst impact
- Degraded
- Components
- MarketingCloudCoreService
- Regions
- db7, db601, db602, db603, db605, db607, db608, db613, db615, db616, db617, db618, db621, db623, db625, db626, db627, db628, db631, db632, db633, db634, db636, db637, db638, db639, db640, db641, db645, db646, db647, db648, db649, db651, db652, db653, db654, db655, db656, db658, db659, db660, db661, db662, db663, db664, db665, db667, db668, db669, db670, db671, db672, db673, db674, db676, db677, db678, db680, db681, db682, db684, db686, db688, db689, db690, db691, db692, db693, db694, db695, db696, db697, db698, db6001, db6002, db6003, db6004, db6005, db6006, db6007, db6008, db6009, db6010, db6011, db6012, db6013, db6014, db6015, db6016, db6018, db6019, db6020, db6021, db6027, db6028, db6029, db6030, db6031, db6032, db6033, db6037, db6039, db6040, db6041
- Down Index
- 43of 100
What to do
Check whether you use Salesforce MarketingCloudCoreService in db7, db601, db602, db603. 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 11h 38m it lasted.
Anything that failed between 2026-10-30 02:00 UTC and 2026-10-30 13:38 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
Between 02:00 and 13:38 UTC on October 30, 2026, a subset of Marketing Cloud Engagement customers on Stack 6 who use branded tracking domains experienced intermittent errors and slow loading when email recipients clicked links. Customers may also have had issues with open tracking and subscription center pages on those domains. Email sending continued normally. A faulty network component that distributes traffic triggered the issue. We removed it from service, which restored service for all affected customers at 13:38 UTC. 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-d151e851b4
Is Salesforce still down?
No, this incident was resolved 2026-10-30 13:38 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
11h 38m, from 2026-10-30 02:00 UTC to 2026-10-30 13:38 UTC, by the times Salesforce posted.
What was affected?
Salesforce named MarketingCloudCoreService in db7, db601, db602, db603.
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.