Tableau Cloud incident
Our three paths to resolution continue in parallel. The memory increase is progressing across additional instances, with the initial instance now stable and serving as the model for the broader rollou
Tableau Cloud is currently experiencing a minor incident affecting EU54 and BRA2S and 1 more component, which began 3h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified Jun 26, 2026, 01:11 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 26, 2026, 01:29 PM UTC
We're investigating an issue where Omnichannel agents are experiencing unexpected disconnections and reconnections, disrupting their ability to manage and receive customer interactions in real-time. We're actively investigating the issue and are still determining the scope of impact. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 26, 2026, 01:37 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 Jun 26, 2026, 01:46 PM UTC
Investigations indicate a recent change as the potential trigger for this issue. We're rolling back the change to see if it resolves the issue. Investigations have highlighted that the impact radius is broader than initially understood. We're updating the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 26, 2026, 01:49 PM UTC
We have observed that the impact has increased and is now disrupted. We have amended the posting to reflect this and highlighted the approximate timings of this transition.
- monitoring Jun 26, 2026, 01:59 PM UTC
We're continuing to work on rolling back the change that was identified as a potential trigger. We're also working to increase capacity. Omnichannel agents continue to experience unexpected disconnections and reconnections, disrupting their ability to manage and receive customer interactions in real-time. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 26, 2026, 02:17 PM UTC
The scope of this issue has now increased as this has been tied to a broader issue. Customers using Salesforce Edge could experience an impact. We're exploring multiple paths to resolution. The rollback of the change is currently in progress and a memory increase is underway. We've discovered a feature that's causing resource consumption and are disabling the feature to see if this helps. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 26, 2026, 03:01 PM UTC
This issue isn't limited to Omnichannel. Any Salesforce Core, MuleSoft, and Tableau customer relying on Salesforce Edge may be affected and may experience connection timeouts, and pages not loading. Our three paths to resolution are underway: the rollback of the change, memory increase, and disabling the feature causing resource consumption. Investigations have highlighted that the impact radius is broader than initially understood. We're updating the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 26, 2026, 03:39 PM UTC
Our three paths to resolution continue in parallel. The memory increase is progressing across additional instances, with the initial instance now stable and serving as the model for the broader rollout. The release rollback has completed validation and we're preparing to apply it in production. We'll provide an update in 30 minutes or sooner, if additional information becomes available.