Tableau Cloud Outage History

Started Oct 24, 2026, 06:36 AM UTC· resolved Oct 27, 2026, 06:54 PM UTC

1. identified Oct 24, 2026, 06:36 AM UTC

   Degradation Started: Tableau feature degradation

2. monitoring Oct 26, 2026, 04:48 PM UTC

   Customers will see an error opening a data source from a workbook: "That page could not be accessed. Either the data source does not exist or you do not have the necessary permissions. Engineers are working on a fix, there is a workaround to access these data sources: Don't open the data source from the workbook's Data Sources list. Go to Explore → Data Sources and select the data source by name. We have a knowledge article published: https://help.salesforce.com/s/articleView?id=005465388&type=1

3. monitoring Oct 26, 2026, 11:53 PM UTC

   The engineering team has identified the root cause and a fix is ready. The release process has started, and we'll confirm once the fix is live.

4. resolved Oct 27, 2026, 06:54 PM UTC

   Resolved: Incident Resolved

Read the full incident report →

Started Oct 13, 2026, 06:36 PM UTC· resolved Oct 16, 2026, 05:25 AM UTC

1. identified Oct 13, 2026, 06:36 PM UTC

   Degradation Started: Tableau performance degradation

2. resolved Oct 16, 2026, 05:25 AM UTC

   Resolved: Incident Resolved

3. monitoring Oct 16, 2026, 06:15 AM UTC

   We've deployed the fix during off-peak hours to the affected US pods, and we've confirmed that workbooks are loading normally again. Originally posted here https://status.salesforce.com/incidents/20004486 We apologize for the impact this incident had on customers and their businesses. We'll complete a full investigation to establish the technical trigger and underlying cause, and we'll put preventive actions in place to stop this from happening again.

Read the full incident report →

Started Oct 13, 2026, 06:36 PM UTC· resolved Oct 17, 2026, 09:24 AM UTC

1. identified Oct 13, 2026, 06:36 PM UTC

   Degradation Started: Tableau feature degradation

2. monitoring Oct 16, 2026, 08:47 PM UTC

   We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Customers using extract-based data sources may see calculated fields renamed. Workbooks and dashboards that depend on those fields may not display correctly. As a workaround, customers can switch to a live connection. A Known Issue article is available with additional details here: https://help.salesforce.com/s/issue?id=a02g700000BteHp We are actively working on a fix and redeployment to mitigate this issue. We will provide an update as soon as more information becomes available.

3. monitoring Oct 17, 2026, 04:29 AM UTC

   We have successfully validated and tested the fix in a lower environment. Initial reports have indicated positive results, and we are working to roll out the fix to the remaining production instances. We will provide an update as soon as more information becomes available.

4. resolved Oct 17, 2026, 09:24 AM UTC

   Resolved: Incident Resolved

5. monitoring Oct 17, 2026, 10:05 AM UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Read the full incident report →

Started Oct 13, 2026, 06:36 PM UTC· resolved Oct 16, 2026, 09:30 PM UTC

1. identified Oct 13, 2026, 06:36 PM UTC

   Degradation Started: Tableau feature degradation

2. monitoring Oct 15, 2026, 06:38 AM UTC

   We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Affected customers may experience dashboards and workbooks failing to load, remaining stuck on "Loading data sources," or taking longer than expected to open. To reduce the impact, we disabled a related feature, and we're working on a fix. We don't have an estimated time for resolution yet and we'll provide an update as additional information becomes available.

3. monitoring Oct 15, 2026, 09:19 AM UTC

   We’ve identified a likely cause related to a recent change that may be causing processes to become deadlocked while loading data sources. We’re working on a code fix to address the suspected cause. Once ready, we’ll test the fix in lower environments before proceeding with production deployment. The previously implemented mitigation of disabling a related feature remains in place to help reduce customer impact. We don’t have an estimated time for resolution yet. We’ll provide another update if additional information becomes available.

4. monitoring Oct 15, 2026, 04:42 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.

5. monitoring Oct 15, 2026, 09:28 PM UTC

   We have validated the fix and are working towards production rollout. The earlier mitigation, which disabled a related feature, remains in effect to limit customer impact. There's no estimated resolution time at this point. We'll share another update when more information is available.

6. monitoring Oct 16, 2026, 01:46 AM UTC

   We've deployed the fix to several instances, and early results are positive. We haven't seen data sources stall when loading in those instances. Deployment to the remaining instances is scheduled for off-peak hours. Customers on instances still awaiting the fix may continue to see data sources stall when loading. We don't have a resolution time yet. We'll provide an update when more information is available.

7. monitoring Oct 16, 2026, 05:55 AM UTC

   As the fix deployment completes in each region and we restore services, we'll move the resolved instances to a separate Trust post so each resolution time is clear.

8. resolved Oct 16, 2026, 09:30 PM UTC

   Resolved: Incident Resolved

9. monitoring Oct 16, 2026, 11:01 PM UTC

   Deployments have completed in all regions, and services are restored for all impacted customers. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Read the full incident report →

Started Oct 13, 2026, 01:20 PM UTC· resolved Oct 13, 2026, 06:10 PM UTC

1. identified Oct 13, 2026, 01:20 PM UTC

   Disruption Started: Tableau service disruption

2. resolved Oct 13, 2026, 06:10 PM UTC

   Resolved: Incident Resolved

3. monitoring Oct 13, 2026, 06:40 PM UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the service disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Read the full incident report →

Started Oct 12, 2026, 07:30 PM UTC· resolved Oct 13, 2026, 04:00 PM UTC

1. identified Oct 12, 2026, 07:30 PM UTC

   Degradation Started: Tableau feature disruption

2. resolved Oct 13, 2026, 04:00 PM UTC

   Resolved: Incident Resolved

3. monitoring Oct 15, 2026, 08:55 PM UTC

   We resolved an issue where some Prep flows that appended to a published data source showed fewer records than expected in the output data source. We applied a fix and restarted affected services. Affected customers can run a full refresh with the Create output option to refresh the data source. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

4. monitoring Oct 15, 2026, 10:07 PM UTC

   We have published the following Knowledge Article which provides specific instructions and recommendations for customers who may have been affected by this issue: https://help.salesforce.com/s/articleView?id=005461980&type=1

Read the full incident report →

Started Oct 12, 2026, 07:30 PM UTC· resolved Oct 12, 2026, 11:45 PM UTC

1. identified Oct 12, 2026, 07:30 PM UTC

   Degradation Started: Tableau feature disruption

2. resolved Oct 12, 2026, 11:45 PM UTC

   Resolved: Incident Resolved

3. monitoring Oct 15, 2026, 08:52 PM UTC

   We resolved an issue where some Prep flows that appended to a published data source showed fewer records than expected in the output data source. We applied a fix and restarted affected services. Affected customers can run a full refresh with the Create output option to refresh the data source. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

4. monitoring Oct 15, 2026, 10:14 PM UTC

   We have published the following Knowledge Article which provides specific instructions and recommendations for customers who may have been affected by this issue: https://help.salesforce.com/s/articleView?id=005461980&type=1

Read the full incident report →

Started Oct 06, 2026, 03:58 AM UTC· resolved Oct 06, 2026, 06:10 PM UTC

1. identified Oct 06, 2026, 03:58 AM UTC

   Degradation Started: Tableau feature degradation

2. monitoring Oct 06, 2026, 04:56 PM UTC

   Some Tableau users may be unable to view projects if they are not a creator or administrator.

3. monitoring Oct 06, 2026, 05:27 PM UTC

   We're continuing to investigate limited project visibility affecting some Tableau Cloud users without Creator or Administrator roles. We've attempted a feature flag change to help restore visibility. If that doesn't resolve the issue, we'll roll back to the previous version. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. resolved Oct 06, 2026, 06:10 PM UTC

   Resolved: Incident Resolved

5. monitoring Oct 06, 2026, 06:17 PM UTC

   The configuration change we implemented did not resolve the issue affecting some Tableau Cloud users who can't view their assigned projects. We've begun rolling back the recent platform update we believe to have introduced this issue and are closely monitoring the rollback's progress. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring Oct 06, 2026, 06:50 PM UTC

   Some Tableau Cloud users without Creator or Administrator roles were unable to view or access projects and workbooks assigned to them. We rolled back the recent platform update that introduced this issue, and project access is now fully restored. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Read the full incident report →

Started Aug 07, 2026, 07:10 PM UTC· resolved Aug 07, 2026, 07:35 PM UTC

1. identified Aug 07, 2026, 07:10 PM UTC

   Disruption Started: Tableau service disruption

2. resolved Aug 07, 2026, 07:35 PM UTC

   Resolved: Incident Resolved

3. monitoring Aug 07, 2026, 08:22 PM UTC

   We are aware of an issue that impacted Tableau Cloud between 19:10 - 19:35 UTC. During that time, some users may have been unable to log in or may have seen 500 errors when attempting to log in. The impact has currently ceased, but we are actively investigating the technical trigger and taking the appropriate actions to prevent future impact. We will provide an update in 60 minutes or sooner if more information becomes available.

4. monitoring Aug 07, 2026, 08:43 PM UTC

   Further investigation has revealed that the scope of impact is broader than initially understood. Customers may have experienced issues across Tableau services, including but not limited to: Explore, Homepage, Load a View, Web Edit, Refresh an Extract, and Bridge. We will provide an update in 60 minutes or sooner if more information becomes available.

5. monitoring Aug 07, 2026, 09:36 PM UTC

   We have identified the technical trigger as a database-related issue, which has since subsided. Following a comprehensive analysis, we have confirmed that all affected services have returned to normal health. We apologize for how this incident affected you and your business. We will undertake a full investigation to establish the underlying cause and preventive action to avoid a repeat in the future.

Read the full incident report →

Started Aug 04, 2026, 01:00 PM UTC· resolved Aug 07, 2026, 11:04 PM UTC

1. identified Aug 04, 2026, 01:00 PM UTC

   Degradation Started: Tableau feature degradation

2. monitoring Aug 06, 2026, 07:33 PM UTC

   The engineering team is investigating availability issue causing some users to experience errors when loading a view. This affects customers using published data sources or composable data sources.

3. monitoring Aug 06, 2026, 08:36 PM UTC

   We’ve implemented a solution to reduce the impact of the issue causing the feature degradation. Customers should see an improvement when loading views. Engineers will continuing to monitor the effectiveness of the mitigation.

4. monitoring Aug 06, 2026, 11:56 PM UTC

   Engineers are continuing to monitor the mitigation for reducing the errors during load a view, we expect to have the next update after business hours tomorrow August 7th.

5. monitoring Aug 07, 2026, 05:45 PM UTC

   We have seen some improvement to the environment, but we are aware that there is still impact to some sites using published data sources or composable data sources. Tableau engineers are continuing to work towards a solution to mitigate this impact.

6. resolved Aug 07, 2026, 11:04 PM UTC

   Resolved: Incident Resolved

7. monitoring Aug 08, 2026, 12:02 AM UTC

   We’ve implemented a solution to further reduce the impact of the degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely until the next peak traffic period on Monday, when we will provide the next update.

8. monitoring Aug 10, 2026, 05:17 PM UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Read the full incident report →

Started Jul 13, 2026, 08:30 AM UTC· resolved Jul 13, 2026, 12:07 PM UTC

1. identified Jul 13, 2026, 08:30 AM UTC

   Degradation Started: tableauPerformanceDegradation

2. monitoring Jul 13, 2026, 08:52 AM UTC

   We’re investigating an issue impacting the Tableau Public site where customers may encounter a maintenance page, HTTP 502 errors, or request timeouts when attempting to access the site. The impact is currently limited to Tableau Public site. We’re investigating the cause of the issue and working to restore normal service. We've confirmed that the incident start time is earlier than initially reported and have updated this Trust post to reflect the correct start time. We will provide an update in 30 minutes or sooner if new information becomes available.

3. monitoring Jul 13, 2026, 10:00 AM UTC

   We continue to investigate the issue impacting the Tableau Public site. We've implemented few changes and are monitoring the service to evaluate their effectiveness. Although the site may load intermittently, published content and related services may remain unavailable. We will provide another update in 60 minutes or sooner if new information becomes available.

4. monitoring Jul 13, 2026, 11:18 AM UTC

   We're seeing improved service stability following the changes we've implemented and are continuing to monitor the service. While Tableau public site is accessible, some customers may still experience intermittent issues accessing published content and related services. We will provide another update in 60 minutes or sooner if new information becomes available.

Read the full incident report →

Started Jun 26, 2026, 01:56 PM UTC· resolved Jun 26, 2026, 06:10 PM UTC

1. identified Jun 26, 2026, 01:56 PM UTC

   Degradation Started: tableauFeatureDegradation

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

Read the full incident report →

Started Jun 22, 2026, 02:41 PM UTC· resolved Jun 22, 2026, 03:42 PM UTC

1. identified Jun 22, 2026, 02:41 PM UTC

   Degradation Started: tableauPerformanceDegradation

2. monitoring Jun 22, 2026, 03:17 PM UTC

   We’ve implemented a solution to resolve the issue causing the performance degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jun 18, 2026, 06:48 AM UTC· resolved Jun 18, 2026, 07:01 AM UTC

1. identified Jun 18, 2026, 06:48 AM UTC

   Degradation Started: performanceDegradation

Read the full incident report →

Started Jun 07, 2026, 12:56 AM UTC· resolved Jun 07, 2026, 02:31 AM UTC

1. identified Jun 07, 2026, 12:56 AM UTC

   Disruption Started: maintenanceOverrunServiceDisruptionBegan

Read the full incident report →

Started May 13, 2026, 05:54 PM UTC· resolved May 13, 2026, 06:27 PM UTC

1. identified May 13, 2026, 05:54 PM UTC

   Disruption Started: tableauServiceDisruption

Read the full incident report →

Started May 11, 2026, 08:12 PM UTC· resolved May 11, 2026, 08:26 PM UTC

1. identified May 11, 2026, 08:12 PM UTC

   Degradation Started: performanceDegradation

2. monitoring May 11, 2026, 08:12 PM UTC

   We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

Read the full incident report →

Started May 07, 2026, 04:18 PM UTC· resolved May 07, 2026, 04:54 PM UTC

1. identified May 07, 2026, 04:18 PM UTC

   Disruption Started: tableauServiceDisruption

Read the full incident report →

Started May 05, 2026, 04:55 AM UTC· resolved May 05, 2026, 06:13 AM UTC

1. identified May 05, 2026, 04:55 AM UTC

   Disruption Started: tableauServiceDisruption

2. monitoring May 05, 2026, 04:57 AM UTC

   At 03:13 UTC, May 5, 2026, we noted an issue impacting online Tableau Cloud services where multiple POD’s may be impacted due to Multi-Factor Authentication issues (MFA). Customers trying to log into their Tableau Cloud sites using MFA may have trouble with login issues. We're ‌actively engaged and are exploring multiple paths to resolution. We’ll keep you posted in 30 minutes or sooner, once additional information is available.

3. monitoring May 05, 2026, 05:23 AM UTC

   Our initial investigation indicates that authentication requests to a backend verification service are failing with authorization errors preventing successful login attempts. We've initiated a rolling restart on one of the impacted PODs and initial testing looks positive. We're now proceeding ‌with a rolling restart of services for the other impacted POD’s. We remain focused on stabilizing these services and are actively monitoring the environments. We’ll share the next update in 30 minutes or sooner, once additional information is available.

4. monitoring May 05, 2026, 05:51 AM UTC

   The rolling restart is currently underway for the remaining POD’s. We’re actively monitoring each environment post-restart to confirm full recovery. We’ll share the next update in 60 minutes or sooner as additional information is available.

Read the full incident report →

Started May 05, 2026, 02:44 AM UTC· resolved May 05, 2026, 03:51 AM UTC

1. identified May 05, 2026, 02:44 AM UTC

   Degradation Started: tableauPerformanceDegradation

Read the full incident report →