Salesforce favicon

Salesforce outage on 2026-11-11

salesforce.com
November 2026 11 Minor incident

Salesforce logged five separate incidents on 11 November 2026, touching MuleSoft, Heroku and core Apex deployment across dozens of instances. The longest confirmed run lasted just over three hours, and one security advisory was still open with no end time given. All five were filed and resolved on Salesforce's own status page, not yours.

Started

01:57 UTC

Duration

Lasted 19m

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: ARE2S, BRA2S, BRA54S, BRA6S, CHE26S, CHE2S, CS236, CS237, CS238, CS239, CS240, CS241, CS242, CS243, CS244, CS245, CS246, CS247, CS248, CS250, CS251, CS252, CS253, CS254, CS255, CS256, CS257, CS258, CS259, CS260, CS262, CS263, CS264, CS265, CS266, CS267, CS268, CS269, CS270, CS271, CS272, CS275, CS283, CS321, DEU114S, DEU12S, FRA12S, FRA24S, FRA2S, FRA6S, FRA96S, GBR106S, GBR108S, GBR110S, GBR2S, GBR42S, GBR44S, GBR90S, GBR92S, ITA22S, ITA2S, SGP2S, SWE2S, SWE30S, SWE60S, SWE6S, SWE88S, SWE90S, SWE92S, SWE94S, SWE96S, USA20S, USA224S, USA240S, USA244S, USA250S, USA252S, USA254S, USA256S, USA258S, USA260S, USA262S, USA268S, USA270S, USA28S, USA30S, USA3S, USA710S, USA752S, USA754S, USA756S, USA758S, USA760S, USA762S, USA764S, USA766S, USA768S, USA770S, USA772S, USA774S, USA80S, USA870S, USA872S, USA714

What happened?

The day opened at 01:57 UTC with a 19 minute performance degradation that carries no further detail in Salesforce's updates. At 02:40 UTC a MuleSoft issue hit Runtime Fabric customers who manually upgrade their applications: affected apps kept running but could not send logs, metrics or metering data to Anypoint Monitoring while Salesforce reverted a recent change. That one closed in 29 minutes. A security advisory concerning GoFundMe Pro connected applications opened at 11:55 UTC and has no updates and no resolution time on record, so it is still open. At 18:16 UTC a Heroku service degradation hit Private Spaces in the Tokyo region, caused by an issue with an upstream cloud provider that stopped new dyno instances booting; running dynos were not affected. Salesforce posted three updates on that one over roughly two hours before it closed at 3h 1m, tracking the upstream provider's partial, then continued, recovery. Seven minutes later, at 18:23 UTC, a separate feature disruption began affecting customers on instances that had just received a release: Apex code compiling and deploying intermittently failed, and some customers couldn't log in or complete processes depending on that code. Salesforce identified an update to a supporting runtime library as the likely trigger, halted further rollout of the release, and rolled affected instances back to the previous version over five updates and 2h 18m. Across all five incidents, 105 components were listed as in scope at various points, from USA714 and ACCOUNTENGAGEMENT down to several CS-prefixed instances. No user reports were filed during the window on any of these five. Salesforce's own filings are the only record of what happened; there is no independent confirmation beyond their status page.

Learning

None of these incidents show an our_probes entry on this page, which means the picture here comes entirely from what Salesforce chose to publish, not from an external check hitting their endpoints during the window. That matters because the failures described, a reverted library change, a blocked dyno boot process in one region, an Apex compile failure tied to a specific release, all sit inside Salesforce's infrastructure and deployment pipeline, layers your own monitoring of your integration endpoints cannot see into. If your product calls Salesforce APIs or runs Apex-dependent logins, your side could look perfectly healthy while compiling or deployment quietly failed upstream, and you would have no way to tell from your own logs alone. Salesforce's 90 day history shows 127 incidents with a median duration of 2 hours 5 minutes, so a multi-incident day like this one is not unusual for them. 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.