Tableau Cloud incident
Deployment of the fix continues for the remaining impacted production instances. Teams have made additional progress restoring service and are actively addressing the database connection errors affect
Tableau Cloud experienced a minor incident on June 18, 2026 affecting BRA2S and BRA4S and 1 more component, lasting 14h 55m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 18, 2026, 02:58 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 18, 2026, 03:01 PM UTC
We're aware of an issue impacting agents using record pages within Salesforce following a recent release. Customers are encountering unexpected additional pop-ups when completing activities, preventing them from working normally within the product. We're working on a fix that'll be rolled out to Hyperforce and the remaining instances will receive the fix during the standard release window. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 03:30 PM UTC
We've begun deploying a fix to a prioritized group of impacted HyperForce instances and some customers have begun to recover. We're actively preparing for an expedited deployment to all remaining impacted production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available
- monitoring Jun 18, 2026, 03:49 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.
- monitoring Jun 18, 2026, 04:16 PM UTC
We're continuing to deploy the fix to all remaining impacted production instances as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 05:09 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.
- monitoring Jun 18, 2026, 05:42 PM UTC
We've expanded deployment of the fix to all the remaining impacted instances. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 06:11 PM UTC
Deployment of the fix to all remaining impacted production instances remains in progress. Some instances have encountered issues and teams are working to address these database (DB) connection errors. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 07:52 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004126 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 08:33 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004130 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 10:48 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004133 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 10:49 PM UTC
Deployment of the fix continues for the remaining impacted production instances. Teams have made additional progress restoring service and are actively addressing the database connection errors affecting a subset of instances during deployment. Impact to Service Cloud agent pop-ups has now been resolved for additional groups of customers, and restoration efforts remain focused on the remaining impacted instances. We are closely monitoring instance health as remediation progresses and working to restore all affected customers as quickly as possible. We'll continue to provide updates as additional instances are restored.