Tableau Cloud incident
We've started remapping to the scaled cache cluster, and the change is still deploying. We expect full propagation across all impacted instances to take up to 60 minutes, after which traffic should st
Tableau Cloud experienced a minor incident on September 21, 2026 affecting USA1222 and USA1224 and 1 more component, lasting 2h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 21, 2026, 03:47 PM UTC
Degradation Started: performanceDegradation
- monitoring Sep 21, 2026, 03:47 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 Sep 21, 2026, 04:32 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 Sep 21, 2026, 04:44 PM UTC
We're aware of an issue impacting performance where some customers may experience slower response times or delays when using core services on these instances. We have taken steps to increase system capacity on the impacted instances as we continue to investigate the underlying trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 21, 2026, 05:15 PM UTC
Some customers may still experience slower response times or delays when using core services on the impacted instances. We've identified the trigger of this issue as increased database session activity, which is driving elevated cache response times. We're remapping the impacted instances to a newly scaled cache cluster to help restore normal performance, and we're closely monitoring the situation. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 21, 2026, 05:43 PM UTC
We've started remapping to the scaled cache cluster, and the change is still deploying. We expect full propagation across all impacted instances to take up to 60 minutes, after which traffic should stabilize. Some customers may continue to experience slower response times while this rollout completes. We'll provide an update in 30 minutes or sooner if additional information becomes available.