Salesforce favicon

Salesforce outage on 2026-11-06

salesforce.com
November 2026 6 Minor incident

Salesforce logged three separate incidents on 6 November 2026, the largest a Marketing Cloud Next publishing fault that was still unresolved days later. Across 70 listed components, 12 were marked affected, and the fault traced to Salesforce's own infrastructure rather than anything in your setup.

Started

05:55 UTC

Duration

Lasted 10d 1h

Source

IsDown

Next time

Salesforce is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: DEU38, CS255, AUS68, AUS72, AUS76, AUS82, AUS84, AUS86, AUS102, AUS20S, AUS26S, AUS4S, AUS60, AUS62, AUS64, AUS66, AUS6S, AUS70, AUS74, AUS90, AUS92, CAN52, CHE28, DEU114S, DEU70, FRA104, FRA32, FRA34, FRA36, FRA44, FRA46, FRA4S, FRA50, FRA54, FRA56, FRA66, FRA80, FRA84, FRA88, FRA8S, FRA90, GBR118, GBR120, GBR122, GBR34, GBR36, GBR38, GBR48, GBR50, GBR52, GBR54, GBR56, GBR64, GBR68, GBR72, GBR76, GBR88, GBR94, ITA38, JPN136, JPN140, JPN142, JPN146, JPN22S, SWE10, SWE16, SWE64, SWE70, USA352, USA856

What happened?

The first and biggest incident started at 05:55 UTC under the title "Feature Disruption" and remained open for days, with Salesforce still posting updates on it well past 06:29 UTC on the following days. Two shorter incidents also ran that day: a "Performance Degradation" starting 06:29 UTC that lasted 30 minutes, and a "Performance Degradation - Asynchronous Processing" starting 12:27 UTC that lasted 53 minutes. Neither of those two carried any update text, so nothing further is on record about their cause or scope. The long-running incident is better documented. Salesforce's updates describe Marketing Cloud Next customers unable to publish email content, with affected items stuck in "Processing" status, while emails already published were not affected. By 11:58 UTC Salesforce said it had identified the cause and taken steps to prevent further impact, though it did not name the cause publicly. A later update at 19:04 UTC explained the trigger as a planned deployment of Default Marketing Sites, a new administration feature, whose provisioning process created new Salesforce records and apparently sent some users an unrelated "Welcome to Default Marketing Site" email. Fixes were rolled out in stages over the following days, with Salesforce reporting at 23:47 UTC that only 18 affected instances still awaited deployment, with remaining work scheduled over the next few days. No user reports were filed during the window on record. Twelve of the 70 listed components, including AUS68, AUS72, AUS76 and others in that range, carried the affected marking tied to this incident.

Learning

This incident sat inside Salesforce's Marketing Cloud Next publishing pipeline, a backend processing layer that has nothing to do with whether your own endpoints respond. If you were pinging your own integration points or storefront during this window, they could easily have stayed green while content you tried to publish through Salesforce sat stuck in "Processing" for days. That is not a contradiction: your monitoring checks whether your product is reachable, not whether every internal Salesforce queue is draining content correctly. A fault like this, where the provider's own status page is the only source confirming scope and duration, is exactly the kind of outage that slips past endpoint checks aimed at your own infrastructure. Salesforce's own 90 day history shows 126 incidents with a median duration of 2 hours 6 minutes, so a multi-day fix like this one is well outside the norm even for a provider with frequent, usually brief incidents. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.