Tableau Cloud incident
We're actively addressing the problematic jobs on the impacted instances and are seeing signs of service recovery. As a preventive measure, we will terminate non-essential background jobs to avoid fur
Tableau Cloud is currently experiencing a minor incident affecting FRA12S and FRA98S and 1 more component, which began 3h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified Jun 15, 2026, 09:01 AM UTC
Degradation Started: performanceDegradation
- monitoring Jun 15, 2026, 09:50 AM UTC
and a database overload impacting multiple instances in the eu-west-3, and eu-central-1 regions, triggered by a recent change. We're actively working to reduce database load and restore normal processing. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:07 AM UTC
Customers are experiencing high wait times, with message queue (MQ) processing halted on affected cells.. Investigations have highlighted that the impact radius is broader than initially understood. We've updated the posting to reflect additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring Jun 15, 2026, 10:10 AM UTC
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- monitoring Jun 15, 2026, 10:14 AM UTC
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove DEU112, USA80S, USA244S, USA252S, and USA876 that haven't 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. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:35 AM UTC
We're continuing to work to reduce database load and restore normal processing by addressing problematic jobs on the impacted instances. We apologize for how you and your business may be affected by this incident. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:42 AM 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 15, 2026, 11:04 AM UTC
We're actively addressing the problematic jobs on the impacted instances and are seeing signs of service recovery. As a preventive measure, we will terminate non-essential background jobs to avoid further degradation and support continued stabilization. We'll provide an update in 30 minutes or sooner, if additional information becomes available.