- Level
- confirmed
- Worst impact
- Major outage
- Components
- MCGrowth
- Regions
- aus4s, aus6s, aus20s, aus26s, aus60, aus62, aus64, aus66, aus68, aus70, aus72, aus74, aus76, aus82, aus84, aus86, aus90, aus92, aus102, can52, che28, deu70, deu114s, fra4s, fra8s, fra32, fra34, fra36, fra44, fra46, fra50, fra54, fra56, fra66, fra80, fra84, fra88, fra90, fra104, gbr34, gbr36, gbr38, gbr48, gbr50, gbr52, gbr54, gbr56, gbr64, gbr68, gbr72, gbr76, gbr88, gbr94, gbr118, gbr120, gbr122, gbr136s, ita38, jpn22s, jpn136, jpn140, jpn142, jpn146, jpn156, swe10, swe16, swe64, swe70, usa352, usa856, usa942s, usa1138, usa1160, usa1280, usa1330
Summary
Marketing Cloud Next customers on AUS68, AUS72, AUS76, AUS82, AUS84 and AUS86 cannot publish email content, which may stay in Processing status; already-sent emails are unaffected. Publishing is restored for most who contacted support, and a fix is still in progress.
Written by anthropic/claude-haiku-5.5 from Salesforce's own updates.
What to do
Check whether you use Salesforce MCGrowth in aus4s, aus6s, aus20s, aus26s. 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 1d 23h it lasted.
Anything that failed between 2026-11-06 00:20 UTC and 2026-11-08 00: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.
Updates from Salesforce 7
- 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
- investigatingpotentialcause
We are investigating a potential cause of the issue.
provider
- 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
- update
We have identified the cause of the issue preventing some Marketing Cloud Next customers on the AUS68, AUS72, AUS76, AUS82, AUS84 and AUS86 instances from publishing email content. Affected content may remain in “Processing” status. Sending emails that were already published is not affected. We have taken steps to prevent further impact. We are now working to restore publishing for affected customers and are validating the fix before rolling it out more widely. Customers with an open support case will be contacted directly with steps to resolve the issue. We will provide further update as soon as we have more information.
provider
- update
We have identified the cause of the issue preventing some Marketing Cloud Next Gen customers from publishing email content. Affected content may remain in “Processing” status. Sending emails that were already published is not affected. We have taken steps to prevent further impact. We are now working to restore publishing for affected customers and are validating the fix before rolling it out more widely. Customers with an open support case will be contacted directly with steps to resolve the issue. We will provide further update as soon as we have more information.
provider
- update
We continue to work on a fix for the issue where creating email content associated with a brand can get stuck in a "publishing" status. You can find the link to our known issue page for this incident below: https://help.salesforce.com/s/issue?id=a02g700000DbedJ Please contact support for the current workaround. Additionally, we wanted to provide some details regarding this incident to avoid any confusion. We performed a planned deployment of Default Marketing Sites to support newer features being developed on Marketing Cloud Next. As a result, users may have received an email with the subject “Welcome to Default Marketing Site”. Marketing Sites is a new feature for administering your site settings for Code View Landing Pages and Forms, this was recently provisioned by default to Marketing Cloud Next orgs. Due to this provisioning, new Salesforce records were created by the automated provisioning process to support these features.
provider
- update
We continue working to resolve the issue causing some Marketing Cloud Next email content to remain in a “Publishing” or “Processing” status. During final review, Engineering identified an additional issue in the scheduled remediation and updated the fix with further safeguards and monitoring. We’re preparing the revised change for release while completing end-to-end validation in parallel. Once validation is successful, we’ll activate the fix in an affected sandbox environment and verify recovery before proceeding with the broader rollout. In the meantime, Support-assisted remediation has restored publishing for most customers who contacted us, and the Known Issue article includes steps affected customers can take to restore email publishing. Sending emails that were already published remains unaffected. We’ll provide another update as significant progress is made.
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-611609e476
Is Salesforce still down?
No, this incident was resolved 2026-11-08 00:03 UTC. For Salesforce's live state, see https://down.guide/providers/salesforce.
How long did it last?
1d 23h, from 2026-11-06 00:20 UTC to 2026-11-08 00:03 UTC, by the times Salesforce posted.
What was affected?
Salesforce named MCGrowth in aus4s, aus6s, aus20s, aus26s.
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.