Tableau Cloud incident

We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list.

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on September 19, 2026 affecting USA250S and USA672S and 1 more component, lasting 6h 41m. The incident has been resolved; the full update timeline is below.

Started
Sep 19, 2026, 11:13 PM UTC
Resolved
Sep 20, 2026, 05:54 AM UTC
Duration
6h 41m
Detected by Pingoru
Sep 19, 2026, 11:13 PM UTC

Affected components

USA250SUSA672SUSA760SUSA764SUSA936SAUS102BRA14BRA16BRA18BRA24

Update timeline

  1. identified Sep 19, 2026, 11:13 PM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring Sep 19, 2026, 11:46 PM UTC

    We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.

  3. monitoring Sep 20, 2026, 12:21 AM UTC

    We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.

  4. monitoring Sep 20, 2026, 01:45 AM UTC

    We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. Meanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.