Tableau Cloud incident

We performed a rolling restart on a test instance and have verified that Proactive Monitoring limit alerts have been successfully restored on that instance. We are now applying the same restart across

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on August 17, 2026 affecting USA336 and USA438 and 1 more component, lasting 2h. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 06:08 PM UTC
Resolved
Aug 17, 2026, 08:09 PM UTC
Duration
2h
Detected by Pingoru
Aug 17, 2026, 06:08 PM UTC

Affected components

USA336USA438USA732USA736USA748USA780USA830USA848

Update timeline

  1. identified Aug 17, 2026, 06:08 PM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring Aug 17, 2026, 06:30 PM UTC

    We're investigating an issue affecting Proactive Monitoring limit alerts, where some customers may not receive expected notifications. The impact is limited to customers using the affected limit monitoring functionality, and the underlying Salesforce services remain available. We've narrowed the investigation to the processing of specific monitoring data used to generate these alerts and are working to restore normal alerting functionality. We'll provide another update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Aug 17, 2026, 06:58 PM UTC

    We're continuing to investigate the issue affecting Proactive Monitoring limit alerts for a subset of customers. Our investigation confirms that other monitoring data continues to process normally, and the issue remains isolated to the specific monitoring data used to generate these limit alerts. We've validated the broader monitoring pipeline and are continuing to investigate why the affected limit-monitoring data is not being generated as expected. We'll provide another update in 60 minutes or sooner if additional information becomes available.

  4. monitoring Aug 17, 2026, 07:35 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 Aug 17, 2026, 07:40 PM UTC

    We performed a rolling restart on a test instance and have verified that Proactive Monitoring limit alerts have been successfully restored on that instance. We are now applying the same restart across the remaining affected instances. We'll provide another update once the rolling restarts have completed, or sooner if additional information becomes available.