Tableau Cloud incident

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

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on June 16, 2026 affecting EU49 and SWE18, lasting 2h 7m. The incident has been resolved; the full update timeline is below.

Started
Jun 16, 2026, 02:54 PM UTC
Resolved
Jun 16, 2026, 05:01 PM UTC
Duration
2h 7m
Detected by Pingoru
Jun 16, 2026, 02:54 PM UTC

Affected components

EU49SWE18

Update timeline

  1. identified Jun 16, 2026, 02:54 PM UTC

    Degradation Started: performanceDegradation

  2. monitoring Jun 16, 2026, 03:08 PM UTC

    We're aware of an issue where customers may experience failures in automations, integrations, and business processes that rely on asynchronous processing. Customers using Order Management may experience order fulfillment failures. Other features using this processing pattern may also be impacted. We're actively investigating the root cause. We'll provide an update in 30 minutes, or sooner if new information becomes available.

  3. monitoring Jun 16, 2026, 03:30 PM UTC

    We've identified the trigger of the issue as a recently deployed configuration change. We're working to rollback this change. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring Jun 16, 2026, 03:36 PM UTC

    We've identified the trigger of the issue as a recently deployed configuration change. We're working to rollback this change. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  5. monitoring Jun 16, 2026, 03:57 PM UTC

    We've completed the configuration rollback, and the fix is currently propagating across the impacted environments. We're actively monitoring to confirm resolution and will provide an update in 30 minutes or sooner if additional information becomes available.

  6. monitoring Jun 16, 2026, 04:33 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.