Tableau Cloud incident
Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications a
Tableau Cloud experienced a major incident on May 21, 2026 affecting CS238 and CS240 and 1 more component, lasting 4h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 21, 2026, 10:02 PM UTC
Disruption Started: serviceDisruption
- monitoring May 21, 2026, 10:02 PM UTC
We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
- monitoring May 21, 2026, 10:30 PM UTC
At 20:00 UTC on May 21, 2026, a feature disruption began impacting the Salesforce Core Service in the NA223 instance. As a result, customers may be experiencing intermittent disruptions and degradations due to instability. We are engaged and are actively analyzing the issue to determine a mitigation pathway. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 11:15 PM UTC
We’ve identified a recent networking patch as the potential trigger. Some customers attempting to log in via login.salesforce.com or test.salesforce.com may be experiencing issues. We’ve initiated a reboot of impacted networking hosts as a possible solution. The team continues to analyze the trigger and explore additional remediation pathways. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 11:16 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring May 22, 2026, 12:37 AM UTC
Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications about this issue. We sincerely apologise for how this issue has impacted you and your business.