Tableau Service Disruption

As a preventive measure, we are adding additional database capacity, followed by background process restarts, to the United States - West - (10AY), United States - East - (useast-1), United States - East - (prod-useast-b), United States - West - (UW2B) instances, which are now added to this post. Customers will experience a 10-15 minutes service disruption in their queued jobs, flows, and data extracts activity; however, the failed jobs will auto-start once the activity completes.

The customer impact on Europe - Germany - (EW1A), Asia Pacific - Japan - (prod-apnortheast-a), Asia Pacific - Australia - (prod-apsoutheast-a), Europe - UK - (prod-uk-a) has been mitigated; However, we continue to closely monitor the performance of Europe - Germany (DUB01) for any underlying issues.

We will share the next update by 10:46 UTC, or sooner as more information becomes available.

The database capacity was increased to address the slowness and non-responsiveness of jobs, flows, and extracts. The background services were restarted. We are seeing positive results and are monitoring the queue backlog to prevent recurrence.

We will share the next update by 10:20 UTC, or sooner as more information becomes available.

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.

Increasing the database capacity has helped reduce spikes and stabilise connections. We are closely monitoring to confirm if performance has improved. We are still seeing an impact on DUB01 and continue to investigate any underlying issue that might be causing this.

We’re actively working on a resolution and will share the next update by 09:20 UTC, or sooner as more information becomes available.

We’ve identified that Flow runs are also impacted, with longer-than-usual processing times. The issue is impacting more customers than we first believed, including those on DUB01, who will now receive updates for this incident.

To help fix the issue, we’ve increased the database capacity and are closely monitoring the results.

We’re actively working on a resolution and will share the next update by 08:35 UTC, or sooner as more information becomes available.

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.

We are actively assessing the recent changes to determine the quickest path to full restoration. Furthermore, we are exploring options such as a rollback or a configuration update to resolve the issue as quickly as possible.
Please note that this issue is only impacting extract refreshes while all other Tableau functionality remains operational.

We are actively working toward a resolution and will provide further updates at 07:46 UTC or sooner as more information becomes available.

At 01:00 UTC on July 24, 2025, a performance degradation began impacting the extract refresh jobs in the Tableau POD ANAA (Japan). Customers in the affected region may experience extract jobs running slowly or getting stuck in the queue.
Please note that this incident is only impacting extract refreshes while all other Tableau functionality remains fully available.
We are actively engaged and exploring multiple paths to resolution. Remediation efforts are in progress, including reducing the number of active extract processes and restarting services to help restore the job performance.

We will provide an update at 06:50 UTC or sooner as more information becomes available.