Salesforce favicon

Salesforce outage on 2026-10-15

salesforce.com
October 2026 15 Minor incident

If your dashboards sat stuck on "Loading data sources" on 15 October, the fault was on Salesforce's side. A Tableau Cloud release triggered a feature degradation that ran 40 hours and 31 minutes, with a separate, unrelated 17 minute performance issue earlier the same morning.

Started

06:34 UTC

Duration

Lasted 1d 16h

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 longer incident started at 06:34 UTC and was tied by Salesforce to a recent release affecting Tableau Cloud. Affected customers saw dashboards and workbooks fail to load, get stuck on "Loading data sources," or open far slower than normal. Salesforce's first update at 06:38 said a related feature had been disabled to reduce impact while a fix was worked on, with no estimated resolution time given. By 09:19 Salesforce had named a likely cause: a recent change that could leave processes deadlocked while loading data sources, and said a code fix was being tested before production rollout. At 16:42 Salesforce widened the scope of the incident itself, stating the impact radius was broader than first understood and that newly affected instances would get their own communications going forward. By 21:28 the fix was validated and rollout towards production was underway, still with the feature-disable mitigation in place and no resolution time quoted. A further update at 01:46 the next day reported the fix deployed to several instances with positive early results, though instances still awaiting it could keep seeing data sources stall. The final update, at 05:55, said resolved instances would be split into a separate Trust post as the rollout completed region by region, which is also why this page records a single combined duration rather than a clean end time. A second, separate incident, a performance degradation, started at 07:33 UTC and lasted 17 minutes, with no further updates published on it. No components are listed as affected in Salesforce's own breakdown for either incident. No user reports were filed during the window for this page.

Learning

This was a Tableau-specific feature failure inside Salesforce's own data-loading pipeline, not a network or availability problem that an external check against a login page or API endpoint would necessarily catch. A process deadlocking while loading a data source shows up as a slow or stuck dashboard to a person using it, but it does not reliably show up as a failed HTTP request to a simple uptime probe, which is why external monitoring and a real, hours-long user-facing outage can both be accurate at once. Salesforce's own count of 111 incidents in the last 90 days, with a median duration of 2 hours 14 minutes, shows this one ran far longer than typical even before the scope was widened mid-incident. If your own monitoring only watches your endpoints, an incident like this, buried inside a specific feature on the provider's side, can run for days before you notice anything beyond "Salesforce feels slow today". 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.