Tableau Cloud Outage History

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

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.

We're aware of an issue impacting performance where some customers may experience slower response times or delays when using core services on these instances. We have taken steps to increase system capacity on the impacted instances as we continue to investigate the underlying trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Some customers may still experience slower response times or delays when using core services on the impacted instances. We've identified the trigger of this issue as increased database session activity, which is driving elevated cache response times. We're remapping the impacted instances to a newly scaled cache cluster to help restore normal performance, and we're closely monitoring the situation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've started remapping to the scaled cache cluster, and the change is still deploying. We expect full propagation across all impacted instances to take up to 60 minutes, after which traffic should stabilize. Some customers may continue to experience slower response times while this rollout completes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.

We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.

We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. Meanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.

We're investigating an issue impacting a database supporting Marketing Cloud Engagement, and customers on the impacted database are currently unable to connect. Our investigation points to a potential file lock as the trigger. We've engaged additional support and are preparing a secondary environment in case it is needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate a disruption impacting a database supporting Marketing Cloud Engagement, and affected customers remain unable to connect. We've identified that a storage-level lock is likely preventing the database from completing recovery, and our engineering teams are working to resolve it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've ruled out a storage-level file lock as a factor in the ongoing recovery issue impacting Marketing Cloud Engagement. Affected customers remain unable to connect to services on the impacted database. We've started taking the database offline and bringing it back online in an effort to complete recovery. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've performed an in-place restart of the impacted Marketing Cloud Engagement database which has moved into a recovery state. Affected customers remain unable to connect to services while recovery completes. We're monitoring progress closely. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Affected customers remain unable to connect to the Marketing Cloud Engagement database affected by this incident. We're now evaluating whether to continue recovery efforts on this database or move forward to our secondary database, which is fully prepared. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to work on restoring the Marketing Cloud Engagement database. A replacement of a failed component on the storage array has been planned, and is expected to take a few hours. The replacement will run parallel to our recovery work without affecting it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

The Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.

We are investigating a potential cause of the issue.

We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

We’re investigating an issue affecting Agentforce session scoring and tagging functionality for a subset of customers. Our teams are actively working to identify the trigger and restore service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We’re continuing to investigate an issue affecting Agentforce session scoring and tagging for a subset of customers. Our teams are analyzing processing failures and reviewing affected customer environments to determine the trigger and identify a path to restore functionality. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Our teams have narrowed the investigation to failures occurring during session processing and are working to identify a path to restore functionality. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.

We're aware of the issue affecting credit card transactions on Commerce Cloud, where customers are unable to complete purchases using credit cards at checkout. We're restarting the affected applications to restore transaction processing and working on a broader fix to resolve this for all impacted customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We've applied manual fixes across all known affected environments to restore credit card transaction processing on Commerce Cloud checkouts. We're now testing an automated, fleet-wide fix to fully resolve this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. Thank you for your patience as we work to resolve this issue.

We isolated the issue and are working to find the best path to resolution. We will provide an update in 30 minutes or sooner if we have more information.

We continue to explore multiple paths to quickly resolve the issue, which include analysing the error logs and additional diagnostic information to determine the potential trigger. We’ll provide an update upon a significant update, or sooner if additional information becomes available.

Data Cloud customers using batch transforms may see completed jobs remain in an outdated status in the user interface. Automated flows, subsequent transforms, or other downstream processes that depend on the status update may not initiate, potentially delaying downstream data processing. Transform jobs continue to complete successfully, and no impact to the processed data has been identified. We have identified the trigger and initiated a rollback which is expected to remediate the issue. We will provide an update upon completion of the roll back, or sooner if more information becomes available.

As we complete the rollback on individual instances, we will post instance-level updates to accurately reflect each instance’s impact end time. Once an instance has been rolled back, we will remove it from this main post. Instances where rollback is still in progress will continue to receive updates in this post until remediation is complete.

Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users may now experience that their manual and scheduled transform runs fail to start. This was first identified at 20:10 UTC, September 3. We will provide the next update once we can clarify how long the fix-forward will take to verify and deploy, or when new information becomes available. We apologize for any inconvenience this is causing to customers.

We have identified an issue where customers viewing Agent Broker and Flex Gateway metrics are seeing zero values instead of expected data. Our teams have identified the technical trigger and are currently testing and validating a fix before deploying it to all affected areas. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We don’t have any updates to provide at this time, as we’re still testing and validating the potential fix. More information will be provided as soon as it becomes available.

Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We're investigating an issue affecting a subset of sandbox and production environments where users may experience their sessions expiring shortly after signing in, requiring them to authenticate again. We've identified a recent change that may be contributing to the issue and are deploying a configuration change to mitigate the impact. We're monitoring the rollout and validating recovery. We'll provide an update in 30 minutes or sooner as more information becomes available.

We’ve identified some private spaces on which customers might not be able to deploy new applications, update existing applications, scale applications up or down, or restart applications. MuleSoft engineering is working on a mitigation, during which, impacted customers will observe their applications being graceful terminated and restarted. No action is needed from customers during this operation We'll provide another update as additional information becomes available.

We have made significant progress restoring most of the private spaces affected by this issue, with the majority now in a healthy state. We're continuing network configuration and certificate management fixes for the remaining spaces so customers can resume deploying, updating, restarting, and scaling applications. We'll provide an update as additional information becomes available.

We've restored all other previously impacted private spaces to normal operation. We continue to work on restoring the impact to private CloudHub 2.0 space in the US-EAST-1 region where customers may be unable to deploy, update, restart, or scale their applications. We'll provide an update as additional information becomes available.

Starting at 09:34 UTC on August 30, 2026, we identified a service disruption affecting the cart experience in B2B Commerce on Core sandbox environments. As a result, customers in impacted sandboxes are unable to complete certain cart-related workflows, as the underlying API calls used by those workflows are failing. We have identified the source of the issue and are currently evaluating remediation options, while a broader fix is prepared. We will provide an update within 30 minutes or sooner if additional information becomes available.

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.

We identified the technical trigger and confirmed the impact affects most sandbox environments, excluding a subset of specialized environments. We are working on a potential fix and actively working on multiple swim lanes to resolve the issue as soon as possible. We will provide a further update once we have more details to share, or sooner if the situation changes.

We're continuing to work on resolving this issue. Our teams have identified the technical trigger and are working on the fix. We will provide a further update once we have more details to share, or sooner if the situation changes.

We continue working to resolve the disruption affecting cart checkout workflows in B2B Commerce on Core sandbox environments. Having identifed the technical trigger, we’re building a fix-forward release, as deploying this will be the quickest way to restore services to users. This fix is in final testing, and will be deployed to one instance to assess its effectiveness. Following successful monitoring, this will be rolled out to all impacted instances. At present, we’re unable to clarify how long this will take. We’ll provide the next update once we have insight into the viability of the fix-forward deployment. We apologise for any inconvenience this issue is causing to customers.

The fix-forward has been validated as successful, and we are proceeding with a staggered release across all impacted environments. This may take up to 24 hours to complete. We’ll provide a new update if there are any issues with the rollout. We apologize for any inconvenience this issue is causing to customers.

We're investigating an issue where a subset of Commerce Cloud customers are unable to access Business Manager and are seeing a blank page due to a caching issue. This is causing a delay in invoicing and deadlines. Multiple teams have been engaged and are working to restore services. 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations indicate that rolling restarts following a recent release triggered the caching issue. We're manually clearing the cache to resolve the issue and customers are seeing signs of recovery. We'll continue clearing the cache for the remaining impacted PODs. Storefronts aren't impacted. We'll provide an update in 30 minutes or sooner if additional information becomes available.

A subset of customers who received the release continue to experience blank Business Manager pages due to a mismatch of the cache files. Manually clearing the cache is showing signs of recovery, and we continue to clear the cache to restore ‌access to Business Manager. As a workaround, customers can manually clear the cache to restore access by following the steps outlined here: https://issues.salesforce.com/issue/a02g70000085e8H/ 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.