Salesforce favicon

Salesforce outage on 2026-11-09

salesforce.com
November 2026 9 Minor incident

Salesforce's MuleSoft platform had two separate feature problems on 9 November, the longer one lasting 2h 31m. Both were dashboard and API issues on Salesforce's side, not something you could have fixed by changing your own setup.

Started

18:47 UTC

Duration

Lasted 2h 31m

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.

What happened?

The first incident started at 18:47 UTC and ran for 2h 31m. Salesforce reported that the MuleSoft Platform Cost Management dashboard in Enhanced Experience showed no data in the Budget and Optimizations panels, while Mule applications kept running normally and the underlying cost and budget data stayed intact. Salesforce said customers could still reach that data through the available API endpoints, and that no customer action or reconfiguration was needed. Salesforce pointed to a configuration change from a recent release as the likely trigger, and described preparing and validating a targeted fix before rolling it to production, with updates at 19:12 and 20:10 confirming the fix had been deployed to staging and was being pushed to production. At 20:54 Salesforce said the production deployment had started, and at 21:03 it issued a startTimeRevision, saying the original start time of impact had been understood incorrectly and revising it. The second incident began separately at 23:42 UTC and lasted 1h 19m. Salesforce said customers using MuleSoft APIs with SLA-based rate limiting policies could get "401 Unauthorized" errors even with valid client credentials, affecting CloudHub 1.0, CloudHub 2.0, and Hybrid runtimes. Salesforce attributed this to an issue with a feature setting and said a fix began deploying at 23:30 UTC, before the incident was even formally posted. No components are listed as affected on the status page for either incident, and no user reports were filed during either window.

Learning

Both incidents here sat inside MuleSoft's own dashboards and API gateway logic, a layer that an external check hitting your own endpoints would never see, because your product was never broken, Salesforce's cost dashboard and its rate-limiting feature were. The first incident is also a reminder that vendor start times are not fixed: Salesforce revised when impact actually began after the fact, which means any duration calculated from the original post would have understated it. Salesforce's own 90 day history shows 122 incidents with a median duration of 2 hours 6 minutes, so a multi-hour MuleSoft issue is not unusual for this platform. The second incident, with 401 errors on valid credentials, is the kind of failure that looks like a problem in your authentication code until you check the status page and find Salesforce naming a feature setting as the cause. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.</learned>

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.