Tableau Cloud incident
Following the application of a manual fix to selected instances, Data 360 data stream failures have been resolved. Customers who were experiencing impact have been confirmed that normal service has be
Tableau Cloud experienced a minor incident on July 6, 2026 affecting BRA2S and BRA4S and 1 more component, lasting 9h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 06, 2026, 07:18 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Jul 06, 2026, 07:21 AM UTC
Data 360 customers are unable to ingest data, as data stream jobs are failing or becoming stuck, which is stopping downstream business processes. We identified a recent deployment as the likely trigger. We're working to determine the appropriate remediation steps. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 07:52 AM UTC
A service version upgrade deployed over the weekend appears to have introduced a permissions issue preventing jobs from accessing required files. We're comparing the impacted environment with a healthy environment to confirm the trigger, and we're evaluating a rollback to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 09:17 AM UTC
Our investigation has confirmed that the impact extends across multiple instances. The issue is broader than initially understood, and we’ve updated the Trust post to reflect all impacted instances. Data 360 customers on impacted instances are still unable to run data stream jobs, disrupting data ingestion and downstream processes.We’re continuing to validate a confirmed permissions issue preventing the Data Connector Service from starting on impacted instances. A full rollback isn’t possible, so we’re evaluating a targeted redeployment to determine if this can restore the services. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 09:50 AM UTC
A configuration gap introduced during a recent deployment has been identified as the trigger, affecting services on the impacted instances. We’re now implementing a targeted fix, starting with a controlled validation on a lower-impact instance before rolling it out to remaining environments. We’re also verifying that no automated processes will reverse the change. Monitoring is active as we work toward full service restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 10:31 AM UTC
We’ve deployed a manual fix to the first impacted environment and are validating service restoration through live traffic. Once validation is confirmed, we will roll out the fix across all remaining instances. We’re also working with our cloud infrastructure provider to determine how the deployment introduced the permission gap and to ensure automated processes do not reintroduce the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 11:26 AM UTC
The missing permissions policy that was manually added to the impacted instances as a manual fix is showing no errors. We're applying the same fix to the remaining impacted instances in parallel and verifying that no automated process will overwrite the manual change during rollout. Data 360 customers on impacted instances are still unable to run data stream jobs, disrupting data ingestion and downstream processes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 11:59 AM UTC
The manual fix has successfully resolved the errors and monitoring confirms the previously observed errors haven't recurred. We're analyzing logs to validate the fix, as both successful and failed jobs are present on the impacted instances. We're continuing to work on remediating the issue to restore services. We apologize for the inconvenience this is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 12:27 PM UTC
Validation of the fix is in progress and we're continuing to work on remediating the issue to restore services. Data 360 customers may still be unable to run data stream jobs, disrupting data ingestion and downstream processes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 02:19 PM UTC
The manual fix resolved the Data 360 data stream failures on selected instances where the fix was applied. These changes are temporary. We're going to roll back the change that triggered the issue to the last-known stable version. This is expected to take several hours to complete. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jul 06, 2026, 02:41 PM UTC
Following the application of a manual fix to selected instances, Data 360 data stream failures have been resolved. Customers who were experiencing impact have been confirmed that normal service has been restored. The rollback to the last-known stable version is in progress and the rollback is expected to fully resolve the issue. We'll provide an update in 60 minutes or sooner if additional information becomes available.