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 4, 2026 affecting DEU104S and DEU10S and 1 more component, lasting 8h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 04, 2026, 10:15 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Sep 04, 2026, 10:29 AM UTC
We're aware of an issue impacting outbound emails sent from Salesforce using a third-party service as the email provider. Emails are sent successfully from Salesforce; however, recipients aren't receiving the email and the mail server is returning a server busy error. We're investigating the issue and reviewing diagnostic data to identify the trigger, including whether a third-party mail provider is involved. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 10:51 AM UTC
We've identified two error codes tied to this issue, confirming that a third-party provider is limiting inbound mail from Salesforce. We're now working to contact that provider directly to resolve the rate-limiting issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 11:28 AM UTC
A third-party email provider issue continues to impact outbound emails sent from Salesforce. As a result, some customers may experience delayed or failed outbound emails. We're working directly with that provider to resolve the rate limits causing the delay. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 12:03 PM UTC
We've submitted a formal request to engage the third-party provider directly to resolve the rate-limiting impacting outbound email delivery. Customers may still experience delayed or failed outbound emails while we work through this. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 01:05 PM UTC
We're continuing to work with the third-party provider to resolve the rate-limiting issues impacting outbound email delivery. Some customers may continue to experience delayed or failed outbound emails while we work through this. We're investigating in parallel while we wait for their response. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 01:37 PM UTC
We continue to coordinate with our third-party vendor to resolve outbound email delivery issues stemming from rate limits. While some customers may continue to experience delayed or failed outbound emails, impacted messages are delayed, not lost. The system will periodically retry delivery for up to 24 hours. Customers who are locked out because they haven't received a device activation code should contact support for help. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 02:38 PM UTC
We're continuing to work directly with the third-party provider to resolve this issue. This delivery delay affects customers using a specific third-party email provider that is currently limiting the amount of mail it accepts. It isn't caused by any issue with Salesforce's own email system. Impacted outbound emails sent from Salesforce are delayed, not lost — the system will retry delivery for up to 24 hours. Customers who are locked out because they haven't received a device activation code should continue to contact support for help. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 04:09 PM UTC
We’ve been observing steady recovery for outbound emails sent from Salesforce to recipients on several previously affected domains since 13:00 UTC. A smaller subset of messages routed through the third-party provider’s email protection service may continue to experience delivery delays. The provider is applying additional mitigation to address the remaining rate limiting, and telemetry shows fewer newly affected messages as those changes progress. We continue to monitor delivery behavior and will provide another update in 60 minutes or sooner if additional information becomes available.
- monitoring Sep 04, 2026, 04:18 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.