Tableau Cloud incident
We've begun deploying the corrected configuration and are validating the update before proceeding with a broader rollout. Customers may continue to experience Data 360 provisioning failures in sandbox
Tableau Cloud experienced a minor incident on August 18, 2026 affecting CAN20S and CAN2S and 1 more component, lasting 6h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 18, 2026, 09:51 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Aug 18, 2026, 09:58 AM UTC
We're investigating an issue impacting Data 360 provisioning in sandbox environments. Customers may experience failures when attempting to provision Data 360. Initial investigations indicate a recent configuration change that didn't complete successfully as the likely trigger. We're evaluating a rollback of that change in a test environment to confirm it resolves the failures. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 10:07 AM UTC
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
- monitoring Aug 18, 2026, 10:48 AM UTC
The rollback of the recent change is blocked because the build checks are repeatedly failing. We're engaging additional teams to work on alternate measures to resolve build failures. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 11:08 AM UTC
Customers may continue to experience failures when attempting to provision Data 360 in sandbox environments while we work on resolving the build failure blocking the rollback. The changes needed to revert the recent configuration are approved and in progress. In parallel, we've also identified the last known good version to use as a fallback if needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 11:38 AM UTC
We're continuing actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 12:06 PM UTC
We're nearing completion of actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 12:41 PM UTC
The most recent attempt to revert the configuration change didn't complete successfully and we're investigating a new strategy. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 01:10 PM UTC
We're now pursuing an alternative fix, deploying an update with a corrected configuration. We'll provide an update on this in 60 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 02:16 PM UTC
We continue working to resolve Data 360 provisioning failures in sandbox environments by deploying an update with a corrected configuration based on a previously stable version. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Aug 18, 2026, 03:11 PM UTC
We've begun deploying the corrected configuration and are validating the update before proceeding with a broader rollout. Customers may continue to experience Data 360 provisioning failures in sandbox environments while this work is underway. We'll provide an update in 90 minutes or sooner if additional information becomes available.