Tableau Cloud incident
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
Tableau Cloud experienced a minor incident on September 29, 2026 affecting BRA2S and BRA4S and 1 more component, lasting 2h 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 29, 2026, 09:27 PM UTC
Degradation Started: performanceDegradation
- monitoring Sep 29, 2026, 09:38 PM UTC
We’re investigating an issue affecting Data Cloud streaming ingestion in a subset of environments. Customers may experience delays or failures when ingesting data through the Ingestion API, Web and Mobile Connector, or MCP Connector. We’ve identified service startup failures in some affected environments and are evaluating targeted restarts and rollback options to restore normal ingestion. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 29, 2026, 10:03 PM UTC
We’re continuing to investigate the Data Cloud streaming ingestion issue and are moving forward with a rollback in one environment to validate recovery before expanding the action. In parallel, we’re investigating why the service is failing to start normally. We’ll provide another update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 29, 2026, 10:30 PM UTC
We’ve started the rollback in an initial affected environment and are seeing early signs of recovery, though service capacity has not yet returned to expected levels. We’ve narrowed the investigation to a small number of production environments and are manually increasing capacity while validating the rollback. Customers on affected environments may continue to experience delays or failures when ingesting data through the Ingestion API, Web and Mobile Connector, or MCP Connector. We’ll provide another update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 29, 2026, 10:57 PM UTC
We’ve successfully increased service capacity in one of the affected environments, and initial validation confirms the additional service instances are active. We’re applying the same targeted action to the remaining affected environments while addressing the issue that prevented services from scaling automatically. Customers on affected environments may continue to experience delays or failures when ingesting data through the Ingestion API, Web and Mobile Connector, or MCP Connector. We’ll provide another update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 29, 2026, 11:00 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.