Tableau Outage History

Tableau Cloud experienced a 9.5-hour performance degradation that prevented customers from loading embedded Tableau views within Salesforce Lightning Web components, with users encountering "connection refused" errors along with general slow performance, timeouts, and connectivity issues. The issue was traced to a recent deployment in the US West 2 region that handles SSO/Authentication for embedded views. Engineers resolved the incident by rolling back to a previously stable version, with service recovery observed starting at 09:33 UTC.

Tableau Cloud experienced a feature disruption lasting 6 hours that prevented users from successfully running Prep Flows, with the primary impact in the Japan region and minimal occurrences in other regions. The incident affected multiple infrastructure components across several instances, with the impact radius expanding beyond what was initially understood. Engineers resolved the issue by applying configuration changes to the affected infrastructure components, successfully restoring service to the Asia Pacific Japan instance first before applying the same remediation to remaining affected instances.

Tableau Cloud experienced a feature degradation lasting 50.5 hours that affected extract refresh jobs across multiple PODs, with customers using SharePoint Lists JDBC experiencing failures when OAuth connections expired. Engineers identified a recent change as the root cause and developed a fix that was deployed in a staggered rollout across all affected instances. The fix has been successfully deployed and the team is monitoring system performance to ensure continued stability.

Tableau Cloud experienced a major service disruption lasting 1.9 hours that prevented end users from accessing the service entirely, including data connections and the full Tableau ecosystem. The outage affected component PDUEBA, with users reporting complete unavailability of all Tableau services. Tableau engineers worked on the issue and customers began seeing intermittent improvements followed by continued performance recovery as the service was restored.