Tableau Cloud incident
We have successfully validated and tested the fix. Initial reports have indicated positive results and services were restored to normal operating levels for the verification instances.
Tableau Cloud experienced a minor incident on May 16, 2026 affecting ANYPOINTMANAGEMENTCENTER-US and ANYPOINTOBSERVABILITYSUITE-US and 1 more component, lasting 3h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 16, 2026, 12:57 PM UTC
Degradation Started: muleSoftPerformanceDegradation
- monitoring May 16, 2026, 12:59 PM UTC
At 09:30 UTC, May 16, 2026, we identified a performance degradation affecting the Secrets Manager Provider and API in our production environment. As a result, customers attempting to deploy or restart applications may be unable to do so successfully, as secrets cannot be retrieved during this process. Currently running applications that are not restarting are not impacted and will continue to operate normally. We have identified a potential technical trigger and have initiated a remediation process. We are working to restore full service and will provide an update within 30 minutes or sooner if additional information becomes available.
- monitoring May 16, 2026, 01:28 PM UTC
The previous attempt to restore the service didn't yield the desired results. We continue to investigate the issue and analyze data to determine the best path to resolution. We’ll provide an update upon significant update, or sooner if additional information becomes available.
- monitoring May 16, 2026, 02:34 PM UTC
We are working on resolving the impact on runtime manager in the US control plane. Customers using Application Manager will not be able to deploy or re-deploy their applications. We’ll provide an update upon significant update, or sooner if additional information becomes available.
- monitoring May 16, 2026, 03:58 PM UTC
We have successfully validated and tested the fix. Initial reports have indicated positive results and services were restored to normal operating levels for the verification instances. We are reviewing additional logs to confirm the fix. We’ll provide an update upon significant update, or sooner if additional information becomes available.