Tableau Cloud incident
Investigations have shown that the impact also included some customers in the India region who were unable to sign in. We changed Domain Name System (DNS) records to route traffic to healthy instances
Tableau Cloud experienced a minor incident on June 26, 2026 affecting PDPUWAA and 10AYPD and 1 more component, lasting 4h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 26, 2026, 01:56 PM UTC
Degradation Started: tableauFeatureDegradation
- monitoring Jun 26, 2026, 02:08 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 Jun 26, 2026, 02:09 PM UTC
We're aware of an issue affecting the Tableau Cloud sign-in service were subset of customers in European regions are unable to sign in to their Tableau Cloud PODs. We're investigating the trigger of this issue and will provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 26, 2026, 02:35 PM UTC
We believe the trigger has been identified and our teams are working to reroute traffic to healthy infrastructure to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 26, 2026, 03:04 PM UTC
We continue to make progress in restoring service and have rerouted traffic away from the impacted infrastructure to healthy PODs. The majority of the affected customers have access restored, and we’re continuing to apply the same steps for theremaining customers to achieve full restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 26, 2026, 03:21 PM UTC
We continue to make progress in restoring service and will apply the same steps for the remaining impacted customers to achieve full restoration. We'll provide the next update upon a significant development or once full service restoration is confirmed.
- monitoring Jun 26, 2026, 05:42 PM UTC
Investigations have shown that the impact also included some customers in the India region who were unable to sign in. We changed Domain Name System (DNS) records to route traffic to healthy instances, and access has been restored. We're actively monitoring performance and completing health checks to confirm full stability. We'll provide the next update upon a significant development or once full service restoration has been confirmed.