Tableau Cloud incident

Our maintenance activity is progressing as planned. We've completed initial validation of the standby environment and are seeing expected service behavior. We are completing the remaining deployment a

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on August 17, 2026 affecting POD313 and POD240 and 1 more component, lasting 2h 3m. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 03:55 PM UTC
Resolved
Aug 17, 2026, 05:58 PM UTC
Duration
2h 3m
Detected by Pingoru
Aug 17, 2026, 03:55 PM UTC

Affected components

POD313POD240POD241POD270POD271POD284POD285POD330POD331POD194

Update timeline

  1. identified Aug 17, 2026, 03:55 PM UTC

    Degradation Started: ccAccountManagerImpacted

  2. monitoring Aug 17, 2026, 04:01 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.

  3. monitoring Aug 17, 2026, 04:13 PM UTC

    We're investigating an issue affecting Account Manager where customers may experience intermittent errors. To restore service stability, we've initiated maintenance to transition Account Manager to a standby environment. During this activity, Account Manager will remain available in read-only mode, and customers may be unable to make configuration changes. We expect the maintenance activity to take approximately one hour and are closely monitoring progress. We'll provide an update in 90 minutes or sooner if additional information becomes available.

  4. monitoring Aug 17, 2026, 05:36 PM UTC

    Our maintenance activity is progressing as planned. We've completed initial validation of the standby environment and are seeing expected service behavior. We are completing the remaining deployment activity and will then perform additional automated validation before transitioning traffic to the standby environment. We'll continue to monitor progress closely and provide another update in 60 minutes or sooner if additional information becomes available.