Salesforce favicon

Salesforce outage on 2026-11-13

salesforce.com
November 2026 13 Minor incident

On 13 November 2026, Salesforce had two separate incidents, one hitting Setup page performance and another hitting MuleSoft's API Manager, Runtime Manager and Partner Manager in the US region. Both were problems on Salesforce's side, lasting 1h 6m and 1h 8m respectively.

Started

03:12 UTC

Duration

Lasted 1h 6m

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: CAN80, FRA62, GBR58, IDN8, SWE118, USA876, SWE54

What happened?

The first incident started at 03:12 UTC and was logged as performance degradation. Salesforce reported longer page load times and intermittent timeouts on some instances, and said it had identified a recent change that might be the trigger. The impact radius was widened twice, at 03:28 and again at 04:02, meaning more instances were affected than Salesforce first disclosed. That incident ran for 1h 6m before it was resolved. The second incident began at 09:02 UTC and affected MuleSoft API Manager, Runtime Manager and Partner Manager in the US region. Salesforce said customers could not deploy applications or APIs, some saw errors loading the user interface, and requests to the authentication service were timing out, though retries sometimes succeeded. By 09:40 UTC Salesforce said authentication response times had returned to normal at approximately 09:14 UTC and errors had reduced, while it kept investigating the trigger. At 09:50 UTC the impact radius was widened again. That incident lasted 1h 8m in total. Seven components were named across the day: CAN80, FRA62, GBR58, IDN8, SWE118, USA876 and SWE54. No cause was confirmed for either incident; Salesforce flagged a possible trigger for the first one but never confirmed it, and for the second it said only that the trigger was still under investigation. No user reports were filed during this window. Salesforce's own updates are the only record of what happened.

Learning

Both of these incidents sat inside Salesforce's own infrastructure, in Setup page rendering and in MuleSoft's authentication and deployment layers, which means pinging your own endpoints would not have shown you anything wrong. Your product can look perfectly healthy from the outside while Salesforce's Setup pages time out or MuleSoft fails to authenticate deployments behind it. That is why an external check and a real outage can both be true at once: your monitoring is built to watch your own stack, not the provider powering parts of it. Salesforce logged 128 incidents in the past 90 days with a median duration of 2 hours 4 minutes, so this kind of disruption is routine rather than exceptional 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.