Tableau Cloud incident

We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health m

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on June 17, 2026 affecting BRA2S and BRA4S and 1 more component, lasting 1h 31m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 10:50 PM UTC
Resolved
Jun 18, 2026, 12:22 AM UTC
Duration
1h 31m
Detected by Pingoru
Jun 17, 2026, 10:50 PM UTC

Affected components

BRA2SBRA4SBRA54SBRA6SBRA8SDEU104SDEU10SDEU114SDEU116SDEU12S

Update timeline

  1. identified Jun 17, 2026, 10:50 PM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Jun 17, 2026, 10:55 PM UTC

    We're aware of an issue impacting Agentforce. A subset of customers may encounter a "Something went wrong, please try again" error when accessing Agentforce across multiple instances. We're actively investigating potential triggers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Jun 17, 2026, 11:32 PM UTC

    We continue to investigate this issue. We have deployed a fix on one of the impacted instances and are currently monitoring performance. If successfully validated, we will deploy the fix to all impacted instances to restore services as quickly as possible for customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring Jun 17, 2026, 11:59 PM UTC

    We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health metrics across instances that have received the fix so far. We'll provide an update in 30 minutes or sooner if additional information becomes available.