Salesforce favicon

Salesforce outage on 2026-10-16

salesforce.com
October 2026 16 Minor incident

Salesforce logged two separate incidents on 16 October affecting the GBR34 component, including a 13h 36m Tableau feature degradation. Both faults originated on Salesforce's side, tied to a recent release rather than anything in your own setup.

Started

20:30 UTC

Duration

Lasted 13h 36m

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?

Salesforce's status page records two incidents against the GBR34 component on this day. The first, "Performance Degradation - Asynchronous Processing", started at 13:48 and lasted 44 minutes, with no updates published beyond the listing itself. The second, "Tableau Feature Degradation", started at 20:30 and ran for 13h 36m, making it by far the longer of the two. Salesforce's first update, at 20:47, said the issue followed a recent release and affected a subset of Tableau Cloud customers using extract-based data sources, where calculated fields could be renamed and dependent workbooks or dashboards might not display correctly. Salesforce offered a workaround, switching to a live connection, and pointed to a Known Issue article for detail. The next update did not arrive until 04:29, nearly eight hours later, saying the fix had been validated and tested in a lower environment and was being rolled out to remaining production instances. No further update after that closes the incident out on the record, though the listed duration of 13h 36m indicates it was eventually marked resolved. No user reports were filed during the window for either incident. Salesforce's 90 day history shows 111 incidents with a median duration of 2 hours 18 minutes, so the first incident's 44 minutes sits well under typical, while the Tableau incident's 13h 36m sits well over it. Across all time Salesforce has logged 2,475 incidents.

Learning

This incident sat specifically inside Tableau's rendering of calculated fields from extract-based data sources, a problem at the application layer rather than at the network or availability layer, which is why the fix process involved validating in a lower environment before touching production. Watching your own endpoint or dashboard uptime would not have surfaced this, because the service stayed reachable throughout: the symptom was wrong data display, not downtime. That is also why Salesforce's own component list is the only place this showed up until the fix rolled out, over eight hours after the first notice. UptimeRobot's 30 day figures for Salesforce show 35 incidents with 33 resolved and a median duration of 1h 59m, giving you a baseline for how long these typically run. Your own monitoring tells you whether your product is up, but it cannot tell you whether a provider's internal release has quietly broken a feature behind the scenes. 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.