Tableau Cloud incident

The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstream

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on August 24, 2026 affecting SPIFF-US1 and SPIFF-EU1, lasting 1d 11h. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2026, 05:08 PM UTC
Resolved
Aug 26, 2026, 04:53 AM UTC
Duration
1d 11h
Detected by Pingoru
Aug 24, 2026, 05:08 PM UTC

Affected components

SPIFF-US1SPIFF-EU1

Update timeline

  1. identified Aug 24, 2026, 05:08 PM UTC

    Degradation Started: salesforceSpiffFeatureDisruption

  2. monitoring Aug 24, 2026, 05:27 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  3. monitoring Aug 24, 2026, 05:55 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  4. monitoring Aug 24, 2026, 06:30 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  5. monitoring Aug 24, 2026, 07:13 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  6. monitoring Aug 24, 2026, 07:42 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  7. monitoring Aug 24, 2026, 08:12 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  8. monitoring Aug 24, 2026, 08:31 PM UTC

    We have observed that the impact on service health has decreased from a disrupted to a degraded state. We have amended the posting to reflect this and have highlighted the approximate timings of this transition.

  9. monitoring Aug 24, 2026, 09:01 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  10. monitoring Aug 24, 2026, 09:29 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  11. monitoring Aug 24, 2026, 10:01 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  12. monitoring Aug 24, 2026, 11:01 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  13. monitoring Aug 24, 2026, 11:35 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

  14. monitoring Aug 25, 2026, 03:53 AM UTC

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

  15. monitoring Aug 25, 2026, 02:24 PM UTC

    We are investigating a potential cause of the issue.

  16. monitoring Aug 25, 2026, 02:56 PM UTC

    We’re investigating the cause of the issue and have engaged more engineers to help isolate the root cause. We will provide an update in 30 minutes or sooner if we have more information.

  17. monitoring Aug 25, 2026, 04:26 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  18. monitoring Aug 25, 2026, 07:51 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  19. monitoring Aug 25, 2026, 09:34 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  20. monitoring Aug 25, 2026, 10:04 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  21. monitoring Aug 25, 2026, 10:56 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

  22. monitoring Aug 26, 2026, 03:14 AM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.