Tableau Cloud incident
We are continuing to make progress in restoring services. We have successfully restored services on a subset of PODs, and we're actively working through the remaining impacted environments. We are exe
Tableau Cloud is currently experiencing a major incident affecting POD313 and POD219 and 1 more component, which began 2h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified Jun 18, 2026, 01:36 AM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 18, 2026, 01:53 AM UTC
We are aware of a service disruption that began impacting B2C Commerce Cloud. As a result, customers may be unable to access their Commerce Cloud Storefronts and services. We're actively working to restore full service availability. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 02:03 AM UTC
We've identified an infrastructure configuration issue impacting a subset of our PODs. We are actively working to restore affected services. We're currently validating our recovery approach on a subset of environments before applying the fix more broadly. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 02:35 AM UTC
We're continuing to make progress in restoring services. Infrastructure configuration issue prevented a subset of PODs from completing a planned update, which caused those PODs to enter an unhealthy state. We’ve successfully restored a subset of affected PODs and are actively working through the remaining impacted PODs. We're executing the restoration process in parallel to bring all affected services back online as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 03:24 AM UTC
We are continuing to make progress in restoring services. We have successfully restored services on a subset of PODs, and we're actively working through the remaining impacted environments. We are executing the restoration process in parallel to bring all affected services back online as quickly as possible. As PODs are restored, we are publishing individual Trust posts for each instance to accurately capture the service restoration time. Customers on restored instances should refer to their instance-specific post for the end time of this disruption and confirmation that services have been restored. We'll provide an update in 60 minutes or sooner if additional information becomes available.