Is Tableau Cloud down?

Last checked 4m ago
Current status
Tableau Cloud has degraded performance

Active incident: Customers with the Transaction Security Policy enabled are…

Official status page: https://status.salesforce.com/products/Tableau · Polled every 5 minutes · 2792 components tracked

Tableau Cloud is reporting degraded performance right now (last checked 4m ago). Services are up but slower or partially failing.

Real-time Tableau Cloud status, recent outages, and incident history — pulled directly from Tableau Cloud's official status page at https://status.salesforce.com/products/Tableau every 5 minutes. Pingoru tracks 2792 Tableau Cloud services and has captured 155 incidents in the last 90 days (91.59% uptime). Get email, Slack, Discord, or webhook alerts the moment Tableau Cloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tableau Cloud also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Tableau Cloud uptime 91.59% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Active incident 1

  1. Ongoing ● 6h 44m
    Started Jul 29, 2026, 08:51 AM UTC
    USA9402EU54BRA2SBRA4SBRA54SBRA6SBRA8SCAN20SCAN2SCAN4S
    Timeline · 6 updates
    • identified · Jul 29, 2026, 08:51 AM UTC

      Degradation Started: featurePerfDegradation

    • monitoring · Jul 29, 2026, 08:51 AM UTC

      We’re aware that multiple customers are unable to export reports. When customers with the Report Export Transaction Security Policy enabled attempt to export a report, the system prompts them to complete identity verification. After they complete the verification, the export fails with an error. We've identified the trigger as a recent change and are working on a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    • monitoring · Jul 29, 2026, 09:50 AM UTC

      We’ve identified a recent change as the trigger and are working to develop a fix-forward. An approval is in place for this fix forward. Once approved, the fix will be then tested for its effectiveness and deployed to the impacted instances to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    • monitoring · Jul 29, 2026, 10:26 AM UTC

      We're currently testing the fix in a test environment to confirm the fix works as expected. Once testing is complete, the fix will be deployed to the impacted instances and is estimated to take several hours. We'll provide the next update upon a significant change or when more information becomes available.

    • monitoring · Jul 29, 2026, 10:41 AM UTC

      A Known Issue article, which includes an available workaround, can be found here: https://help.salesforce.com/s/issue?id=a02g7000006Yoa1AAC. Customers can apply the workaround to continue operations while the fix is being deployed. Note: If you've applied any workaround steps, please ensure they are reverted once the fix has been deployed. We'll provide the next update upon a significant change or when more information becomes available.

    • monitoring · Jul 29, 2026, 02:18 PM UTC

      Customers with the Transaction Security Policy enabled are experiencing a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completing. This impacts production and sandbox environments, including Hyperforce and GovCloud, and is linked to a recent release. The fix is ready to be deployed to two test instances and is expected to take two hours to complete validations. Following successful validations, the fix will be deployed across all impacted instances. As a temporary workaround, customers can disable the Report Export Transaction Security Policy. If applied, please re-enable the policy once the fix is deployed. We’ll provide another update as additional information becomes available.

    Latest: Customers with the Transaction Security Policy enabled are experiencing a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completin…

Recent outages & incidents

Past 90 days
  1. Resolved 2h 46m
    Started Jul 27, 2026, 02:47 PM UTC · Resolved Jul 27, 2026, 05:34 PM UTC
    ANYPOINTOBSERVABILITYSUITE-US
    Timeline · 5 updates
    • identified · Jul 27, 2026, 02:47 PM UTC

      Degradation Started: muleSoftFeatureDisruption

    • monitoring · Jul 27, 2026, 02:50 PM UTC

      We're aware of an issue affecting MuleSoft Anypoint Visualizer in the US region. Customers may be experiencing an inability to view metrics data and graphs. We're investigating the issue and will provide an update within 30 minutes or sooner if additional information becomes available.

    • monitoring · Jul 27, 2026, 03:22 PM UTC

      We have identified that an accumulation of database logs is consuming storage and contributing to the elevated CPU usage. We are working to resolve this blockage to restore service as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.

    • monitoring · Jul 27, 2026, 04:21 PM UTC

      As our investigation has progressed, we have identified a circular deadlock on the Visualizer database as an additional trigger for the elevated CPU. We are actively working to terminate the blocking sessions responsible for the deadlock. We'll provide an update in 60 minutes or sooner if additional information becomes available.

    • monitoring · Jul 27, 2026, 04:43 PM UTC

      As a result of our remediation efforts, the database CPU has returned to normal levels and blocking sessions have been cleared. We are completing final steps to restore the Visualizer service. We also want to clarify the scope of impact: throughout this incident, the ability to view existing graphs was not affected. Only the metrics ingestion path was disrupted, meaning new metrics data may not have been recorded during the impact window. We'll provide an update in 60 minutes or sooner if additional information becomes available.

    Latest: As a result of our remediation efforts, the database CPU has returned to normal levels and blocking sessions have been cleared. We are completing final steps to restore the Visuali…

  2. Resolved 12m
    Started Jul 27, 2026, 06:12 AM UTC · Resolved Jul 27, 2026, 06:24 AM UTC
    IND172
    Timeline · 1 update
    • identified · Jul 27, 2026, 06:12 AM UTC

      Degradation Started: performanceDegradation

    Latest: Degradation Started: performanceDegradation

  3. Resolved 1h 39m
    Started Jul 24, 2026, 03:21 AM UTC · Resolved Jul 24, 2026, 05:00 AM UTC
    DB12000DB12001DB12003DB12006DB12007DB12009DB12012DB12013DB12015DB12017
    Timeline · 1 update
    • identified · Jul 24, 2026, 03:21 AM UTC

      Degradation Started: performanceDegradation

    Latest: Degradation Started: performanceDegradation

  4. Resolved 1h 31m
    Started Jul 23, 2026, 11:31 AM UTC · Resolved Jul 23, 2026, 01:03 PM UTC
    AP52AP53AP54AP60JPN134JPN138JPN160JPN164
    Timeline · 4 updates
    • identified · Jul 23, 2026, 11:31 AM UTC

      Degradation Started: featurePerfDegradation

    • monitoring · Jul 23, 2026, 11:36 AM UTC

      We're aware of an issue affecting email log retrieval for customers on a subset of instances. Customers are currently unable to retrieve email logs, as requests are taking too long to complete. We became aware of this issue at 11:00 UTC; customers have reported impact as early as 07:30 UTC. There's no workaround available at this time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    • monitoring · Jul 23, 2026, 12:09 PM UTC

      We're continuing to investigate an issue affecting email log retrieval for a subset of customers on impacted instances. Customers are experiencing timeout errors when attempting to retrieve email logs. We've updated the incident start time to 05:18 UTC based on the earliest identified impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    • monitoring · Jul 23, 2026, 12:38 PM UTC

      We've identified that internal automated search activity is consuming excessive resources, degrading the capacity available for this feature. We're actively working to address that activity and restore normal service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    Latest: We've identified that internal automated search activity is consuming excessive resources, degrading the capacity available for this feature. We're actively working to address that…

  5. Resolved 41m
    Started Jul 21, 2026, 01:12 PM UTC · Resolved Jul 21, 2026, 01:54 PM UTC
    USA1022
    Timeline · 1 update
    • identified · Jul 21, 2026, 01:12 PM UTC

      Degradation Started: performanceDegradation

    Latest: Degradation Started: performanceDegradation

See the full Tableau Cloud outage history

150 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Tableau Cloud outage history →

Or sign up free to get alerts when Tableau Cloud breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 155 incidents View full outage history →