Tableau Cloud Outage History

Started Aug 10, 2026, 10:59 AM UTC· resolved Aug 10, 2026, 01:42 PM UTC

1. identified Aug 10, 2026, 10:59 AM UTC

   Disruption Started: marketingCloudDisruption

2. monitoring Aug 10, 2026, 12:14 PM UTC

   We identified a likely backend hardware issue, causing intermittent restarts of the database and repeated periods of disruption. We're working to determine a path to resolution and we'll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Aug 10, 2026, 01:14 PM UTC

   We're continuing to assess the most suitable path to address the intermittent restarts of the database and repeated periods of disruption. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Aug 10, 2026, 01:27 PM UTC

   We've taken measures to mitigate the impact. The last recurrence of disruption was at approximately 12:20 UTC and we're continuing to monitor. We're also addressing the underlying problematic hardware to ensure complete resolution. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 08, 2026, 06:35 PM UTC· resolved Aug 08, 2026, 07:09 PM UTC

1. identified Aug 08, 2026, 06:35 PM UTC

   Degradation Started: marketingCloudFeatureDegradation

2. monitoring Aug 08, 2026, 06:35 PM UTC

   During this time, customers that are unable to complete File Transfer, Data Extract and Import features within Automation Studio. A work around for customers would be to pull small data sets from the API.

Read the full incident report →

Started Aug 07, 2026, 08:22 PM UTC· resolved Aug 07, 2026, 09:40 PM UTC

1. identified Aug 07, 2026, 08:22 PM UTC

   Disruption Started: tableauServiceDisruption

2. monitoring Aug 07, 2026, 08:22 PM UTC

   We are aware of an issue that impacted Tableau Cloud between 19:10 - 19:35 UTC. During that time, some users may have been unable to log in or may have seen 500 errors when attempting to log in. The impact has currently ceased, but we are actively investigating the technical trigger and taking the appropriate actions to prevent future impact. We will provide an update in 60 minutes or sooner if more information becomes available.

3. monitoring Aug 07, 2026, 08:43 PM UTC

   Further investigation has revealed that the scope of impact is broader than initially understood. Customers may have experienced issues across Tableau services, including but not limited to: Explore, Homepage, Load a View, Web Edit, Refresh an Extract, and Bridge. We will provide an update in 60 minutes or sooner if more information becomes available.

Read the full incident report →

Started Aug 07, 2026, 05:11 PM UTC· resolved Aug 07, 2026, 05:49 PM UTC

1. identified Aug 07, 2026, 05:11 PM UTC

   Degradation Started: salesforceSpiffFeatureDisruption

Read the full incident report →

Started Aug 06, 2026, 07:33 PM UTC· resolved Aug 10, 2026, 05:25 PM UTC

1. identified Aug 06, 2026, 07:33 PM UTC

   Degradation Started: tableauFeatureDegradation

2. monitoring Aug 06, 2026, 07:33 PM UTC

   The engineering team is investigating availability issue causing some users to experience errors when loading a view. This affects customers using published data sources or composable data sources.

3. monitoring Aug 06, 2026, 08:36 PM UTC

   We’ve implemented a solution to reduce the impact of the issue causing the feature degradation. Customers should see an improvement when loading views. Engineers will continuing to monitor the effectiveness of the mitigation.

4. monitoring Aug 06, 2026, 11:56 PM UTC

   Engineers are continuing to monitor the mitigation for reducing the errors during load a view, we expect to have the next update after business hours tomorrow August 7th.

5. monitoring Aug 07, 2026, 05:45 PM UTC

   We have seen some improvement to the environment, but we are aware that there is still impact to some sites using published data sources or composable data sources. Tableau engineers are continuing to work towards a solution to mitigate this impact.

6. monitoring Aug 08, 2026, 12:02 AM UTC

   We’ve implemented a solution to further reduce the impact of the degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely until the next peak traffic period on Monday, when we will provide the next update.

Read the full incident report →

Started Aug 06, 2026, 02:30 PM UTC· resolved Aug 06, 2026, 06:31 PM UTC

1. identified Aug 06, 2026, 02:30 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Aug 06, 2026, 04:44 PM UTC

   We are currently investigating a feature degradation impacting a subset of GovCloud customers. Some customers may be unable to send or receive case emails, run automated flows, or use related features including Future Apex and Bulk API. Teams are actively working to identify the trigger and evaluate mitigation options. We will provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Aug 06, 2026, 05:56 PM UTC

   Our teams have identified the trigger as a recent platform update that introduced a new requirement for AI model configuration along with an empty model configuration on the affected instance. Teams are evaluating options to help mitigate the impact. We will provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 04, 2026, 08:55 AM UTC· resolved Aug 04, 2026, 12:25 PM UTC

1. identified Aug 04, 2026, 08:55 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Aug 04, 2026, 09:23 AM UTC

   We continue to investigate an issue affecting Einstein Bots, where event log data is unavailable in Report Explorer for a subset of customers. An initial rollback attempt was unsuccessful. We’ve identified the likely trigger and are preparing a fix. We will provide an update in 30 minutes, or sooner if additional information becomes available.

3. monitoring Aug 04, 2026, 09:47 AM 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.

4. monitoring Aug 04, 2026, 10:01 AM UTC

   We’ve determined that the service is failing to start correctly during the rollback process, and are working to resolve the startup failure and restore the service. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

5. monitoring Aug 04, 2026, 10:40 AM UTC

   We've identified a specific trigger blocking the rollback and we're pursuing an alternative path to restore service. We will provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Aug 04, 2026, 11:20 AM UTC

   We've completed a restart on one impacted instance, which is showing positive signs of recovery. We're monitoring this instance for stability before extending the restart to the remaining impacted instances. We will provide an update in 30 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Jul 31, 2026, 11:21 AM UTC· resolved Aug 04, 2026, 12:41 PM UTC

1. identified Jul 31, 2026, 11:21 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jul 31, 2026, 11:38 AM UTC

   We're investigating an issue impacting Snowflake Zero Copy Connectors, where customers may experience Java Database Connection (JDBC) failures. We've identified the issue and are performing a rolling restart of the connector service to restore functionality. We’ll provide an update in 30 minutes or sooner if more information becomes available.

3. monitoring Jul 31, 2026, 11:58 AM UTC

   The rolling restart has resolved the issue impacting Snowflake Zero Copy Connectors. We’re continuing to monitor the service for any recurrence while validating a long-term fix. We'll provide further updates if customer impact returns or as additional information becomes available.

4. monitoring Aug 03, 2026, 02:23 AM UTC

   The rolling restart has resolved the issue impacting third-party integration tools. We’re continuing to monitor our services for any recurrence while validating a long-term fix. We'll provide further updates if customer impact returns. We apologize for any inconvenience this issue has caused for customers.

Read the full incident report →

Started Jul 29, 2026, 06:23 PM UTC· resolved Jul 30, 2026, 06:54 PM UTC

1. identified Jul 29, 2026, 06:23 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 29, 2026, 06:23 PM UTC

   We have resolved the issue causing authentication loops for customers with the Transaction Security Policy enabled during report exports. The issue was identified as a regression introduced in a recent release. We resolved it by deploying an updated release to the impacted instances. If you applied the temporary workaround and disabled the Report Export Transaction Security Policy, it is important that you re-enable this policy now that the fix has been deployed. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

3. monitoring Jul 30, 2026, 05:44 PM UTC

   The Salesforce Technology team has observed that instance stability and performance remain impacted following the implemented steps. Investigations will now resume to establish and assess an alternative best path forward. The next update will be provided in 30 minutes or sooner if information becomes available.

4. monitoring Jul 30, 2026, 05:44 PM UTC

   While we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively investigating this further to resolve the issue as quickly as possible. As a temporary workaround, customers can disable the Report Export Transaction Security Policy. If applied, please re-enable the policy once the fix is deployed. We'll continue to provide updates as more information becomes available.

Read the full incident report →

Started Jul 29, 2026, 08:51 AM UTC· resolved Aug 01, 2026, 05:17 AM UTC

1. identified Jul 29, 2026, 08:51 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 29, 2026, 08:51 AM UTC

   We’re aware that multiple customers are unable to export reports. When customers with the Report Export Transaction Security Policy enabled attempt to export a report, the system prompts them to complete identity verification. After they complete the verification, the export fails with an error. We've identified the trigger as a recent change and are working on a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 29, 2026, 09:50 AM UTC

   We’ve identified a recent change as the trigger and are working to develop a fix-forward. An approval is in place for this fix forward. Once approved, the fix will be then tested for its effectiveness and deployed to the impacted instances to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 29, 2026, 10:26 AM UTC

   We're currently testing the fix in a test environment to confirm the fix works as expected. Once testing is complete, the fix will be deployed to the impacted instances and is estimated to take several hours. We'll provide the next update upon a significant change or when more information becomes available.

5. monitoring Jul 29, 2026, 10:41 AM UTC

   A Known Issue article, which includes an available workaround, can be found here: https://help.salesforce.com/s/issue?id=a02g7000006Yoa1AAC. Customers can apply the workaround to continue operations while the fix is being deployed. Note: If you've applied any workaround steps, please ensure they are reverted once the fix has been deployed. We'll provide the next update upon a significant change or when more information becomes available.

6. monitoring Jul 29, 2026, 02:18 PM UTC

   Customers with the Transaction Security Policy enabled are experiencing a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completing. This impacts production and sandbox environments, including Hyperforce and GovCloud, and is linked to a recent release. The fix is ready to be deployed to two test instances and is expected to take two hours to complete validations. Following successful validations, the fix will be deployed across all impacted instances. As a temporary workaround, customers can disable the Report Export Transaction Security Policy. If applied, please re-enable the policy once the fix is deployed. We’ll provide another update as additional information becomes available.

7. monitoring Jul 29, 2026, 06:28 PM UTC

   The issue where report exports are triggering authentication loops for customers with Transaction Security Policies has been resolved for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004310 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.

8. monitoring Jul 30, 2026, 06:41 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.

9. monitoring Jul 30, 2026, 08:06 PM UTC

   While we previously indicated this issue would be resolved after deploying a fix, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively investigating this further to resolve the issue as quickly as possible. We apologize for any confusion this may have caused and will continue to provide updates as more information becomes available.

10. monitoring Jul 31, 2026, 04:32 AM UTC

    We have the initial fix deployed to a limited number of instances which did not fully resolve the issue. We identified two issues affecting report exports. Longer-running exports can fail due to repeated authentication prompts, and some exports may also intermittently need a retry to complete successfully. We're actively working on two mitigation efforts in parallel: A temporary configuration change to reduce immediate customer impact by letting longer exports complete, and a permanent fix for the underlying authentication flow, which we're developing and validating now. We'll continue to provide updates as more information becomes available.

11. monitoring Jul 31, 2026, 09:37 AM UTC

    We continue to make progress on the report export issue. The temporary fix, which extends the authentication wait period to improve report export reliability, has been validated and will be deployed to a test environment before production rollout. The rollout will take some time to complete. In parallel, we continue to make progress on the permanent fix for the underlying authentication flow. We will continue to provide updates as more information becomes available.

12. monitoring Jul 31, 2026, 06:36 PM UTC

    Validation and testing of the authentication wait period was successful in our test environments. We will begin rolling this fix out in a staggered manner across all impacted instances and follow the progress closely. This is expected to take several hours to fully complete, and we will provide updates to this post as the release develops. We will continue to provide updates as more information becomes available.

Read the full incident report →

Started Jul 27, 2026, 02:47 PM UTC· resolved Jul 27, 2026, 05:34 PM UTC

1. identified Jul 27, 2026, 02:47 PM UTC

   Degradation Started: muleSoftFeatureDisruption

2. monitoring Jul 27, 2026, 02:50 PM UTC

   We're aware of an issue affecting MuleSoft Anypoint Visualizer in the US region. Customers may be experiencing an inability to view metrics data and graphs. We're investigating the issue and will provide an update within 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 27, 2026, 03:22 PM UTC

   We have identified that an accumulation of database logs is consuming storage and contributing to the elevated CPU usage. We are working to resolve this blockage to restore service as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jul 27, 2026, 04:21 PM UTC

   As our investigation has progressed, we have identified a circular deadlock on the Visualizer database as an additional trigger for the elevated CPU. We are actively working to terminate the blocking sessions responsible for the deadlock. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jul 27, 2026, 04:43 PM UTC

   As a result of our remediation efforts, the database CPU has returned to normal levels and blocking sessions have been cleared. We are completing final steps to restore the Visualizer service. We also want to clarify the scope of impact: throughout this incident, the ability to view existing graphs was not affected. Only the metrics ingestion path was disrupted, meaning new metrics data may not have been recorded during the impact window. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 23, 2026, 11:31 AM UTC· resolved Jul 23, 2026, 01:03 PM UTC

1. identified Jul 23, 2026, 11:31 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 23, 2026, 11:36 AM UTC

   We're aware of an issue affecting email log retrieval for customers on a subset of instances. Customers are currently unable to retrieve email logs, as requests are taking too long to complete. We became aware of this issue at 11:00 UTC; customers have reported impact as early as 07:30 UTC. There's no workaround available at this time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 23, 2026, 12:09 PM UTC

   We're continuing to investigate an issue affecting email log retrieval for a subset of customers on impacted instances. Customers are experiencing timeout errors when attempting to retrieve email logs. We've updated the incident start time to 05:18 UTC based on the earliest identified impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 23, 2026, 12:38 PM UTC

   We've identified that internal automated search activity is consuming excessive resources, degrading the capacity available for this feature. We're actively working to address that activity and restore normal service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 20, 2026, 09:06 AM UTC· resolved Jul 20, 2026, 01:42 PM UTC

1. identified Jul 20, 2026, 09:06 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Jul 20, 2026, 09:20 AM UTC

   We're aware of an issue on USA1274S where customers are experiencing complete disruption following a scheduled maintenance activity in their sandbox environment. We're working towards restoring services as quickly as possible. We'll provide another update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 20, 2026, 09:37 AM UTC

   The sandbox instance failed to return to its original site after a scheduled activity was performed. We're working towards making a configuration change to allow the maintenance activity to complete successfully. We'll provide another update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 20, 2026, 10:09 AM UTC

   We've identified an incorrect database configuration as the trigger for the failed scheduled maintenance activity. We're working towards a local restoration to resolve the configuration issue. We'll provide another update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 20, 2026, 10:44 AM UTC

   We've removed the incorrect configuration entry and the local database restore process is now underway. The restoration is expected to take several hours, following which, the maintenance activity will be completed. We'll provide another update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 20, 2026, 11:19 AM UTC

   The local database restore process is underway, and we’re monitoring the progress of the restore, which is expected to take several hours to complete, following which the maintenance activity is expected to resume. We'll provide the next update when there's a significant update or new information becomes available.

7. monitoring Jul 20, 2026, 12:52 PM UTC

   The local database restore is complete. We're now preparing to resume and complete the maintenance activity, which is expected to take several hours to complete. We'll provide the next update when there's a significant update or new information becomes available.

Read the full incident report →

Started Jul 17, 2026, 06:38 PM UTC· resolved Jul 17, 2026, 10:16 PM UTC

1. identified Jul 17, 2026, 06:38 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring Jul 17, 2026, 06:46 PM UTC

   We're aware of an issue where users may be unable to deploy APIs with Transport Layer Security (TLS) Contexts, view available TLS Contexts, or create and use OAuth connections in Composer. Active Composer flows using OAuth connections may also fail. We're actively investigating the issue and working to restore full service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 17, 2026, 07:08 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.

4. monitoring Jul 17, 2026, 07:25 PM UTC

   We're continuing to investigate an issue impacting MuleSoft services where users may be unable to deploy APIs with Transport Layer Security (TLS) Contexts, view available TLS Contexts, create and use OAuth connections in Composer, or experience failures with active Composer flows using OAuth connections. Customers may also experience impact with API Functional Monitoring and Anypoint Partner Manager v2. Our teams have isolated the issue to an underlying platform component supporting these capabilities and are executing targeted recovery actions to restore service while minimizing additional impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jul 17, 2026, 07:54 PM UTC

   We're continuing to investigate an issue impacting MuleSoft services. - API Manager customers may be unable to deploy APIs with Transport Layer Security (TLS) Contexts or view available TLS Contexts. - Runtime Manager customers may be unable to start new deployments, and Flex Gateway customers may be unable to deploy API configurations. - Composer customers may experience issues with active Composer flows. - Customers using API Functional Monitoring may experience scheduled monitors failing to run their configured API tests. - MuleSoft Agent Scanner is experiencing degraded performance, and - Anypoint Partner Manager v2 customers may experience errors when deploying. Our teams have narrowed our investigation and are executing targeted recovery actions to restore service while minimizing additional impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring Jul 17, 2026, 08:30 PM UTC

   We are observing recovery across the impacted MuleSoft services, and customers should see functionality returning to normal. We continue to closely monitor service health and are performing additional validation and stability activities to help prevent recurrence. We'll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Jul 17, 2026, 09:35 PM UTC

   We continue to observe normal service operation across the impacted MuleSoft services. We have completed the deployment of additional preventative measures and are performing comprehensive validation to confirm service stability. Our teams will continue to closely monitor the environment. We'll provide an update in 90 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 15, 2026, 10:03 PM UTC· resolved Jul 16, 2026, 06:02 AM UTC

1. identified Jul 15, 2026, 10:03 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Jul 15, 2026, 10:37 PM UTC

   Our teams continue to investigate intermittent errors affecting customers' ability to view or apply policies in API Manager in the US region. We currently don’t have any updates to share at this time, but we will provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Jul 15, 2026, 11:52 PM UTC

   Our teams continue to investigate the intermittent errors issue. We don’t have any new updates to share at this time, however we have not seen any errors in the last hour. We will provide an update when significant information becomes available.

4. monitoring Jul 16, 2026, 03:23 AM UTC

   We have identified and validated a fix in a test environment that resolved the issue and we did not observe any intermittent errors. We're now preparing to deploy this fix to the production environment. We'll provide an update when the fix has been fully deployed and validated or if significant information becomes available.

Read the full incident report →

Started Jul 15, 2026, 05:43 PM UTC· resolved Jul 16, 2026, 02:03 AM UTC

1. identified Jul 15, 2026, 05:43 PM UTC

   Disruption Started: marketingCloudAccountEngagementFeatureDisruptionApplication

Read the full incident report →

Started Jul 15, 2026, 02:00 PM UTC· resolved Jul 16, 2026, 06:42 AM UTC

1. identified Jul 15, 2026, 02:00 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Jul 15, 2026, 02:21 PM UTC

   We're investigating an issue impacting the API Analytics service for a subset of customers in the US region, which may result in intermittent issues when using the API Analytics product. We’re working on implementing a fix to restore normal service. We'll provide an update in 30 minutes or sooner if more information becomes available.

3. monitoring Jul 15, 2026, 02:46 PM UTC

   The implemented fix didn’t resolve the issue, and we’re working on identifying the underlying cause while continuing to work toward restoring normal service. We'll provide another update in 30 minutes, or sooner if more information becomes available.

4. monitoring Jul 15, 2026, 03:16 PM UTC

   We're continuing our investigation and are testing a change to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 15, 2026, 03:44 PM UTC

   We've implemented a change to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 15, 2026, 04:13 PM UTC

   We've completed a targeted configuration change to address this issue and we're monitoring the results. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Jul 15, 2026, 04:42 PM UTC

   We've identified that the configuration change we implemented hasn't fully restored service. We're now deploying an updated configuration to allow service instances to stabilize and begin receiving traffic normally. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Jul 15, 2026, 05:10 PM UTC

   We're continuing to investigate. A configuration update intended to stabilize service instances encountered a deployment error and is being retried. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Jul 15, 2026, 05:39 PM UTC

   We're continuing to investigate. Our most recent configuration change hasn't improved service stability, and we're now reverting those changes while pursuing an alternative path to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Jul 15, 2026, 06:09 PM UTC

    We're continuing to investigate. In addition to reverting our most recent configuration changes, we're investigating a potential underlying network routing issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. monitoring Jul 15, 2026, 06:42 PM UTC

    We're continuing to investigate, and engaged additional subject matter experts to assist with diagnosing the underlying network routing issue. In parallel, we're updating a configuration to scale service capacity and remove a dependency that may be contributing to the instability. We'll provide an update in 60 minutes or sooner if additional information becomes available.

12. monitoring Jul 15, 2026, 07:36 PM UTC

    We're continuing to investigate the underlying trigger of this issue. Based on our latest analysis, we're implementing an additional mitigation that updates service health check behavior while maintaining previously applied routing changes. We're monitoring the rollout and validating whether these changes restore service stability. We'll provide an update in 60 minutes or sooner if additional information becomes available.

13. monitoring Jul 15, 2026, 08:36 PM UTC

    We're continuing to investigate the underlying cause of this issue. Based on our latest findings, we're deploying an updated service configuration that adjusts health check behavior while also removing an external dependency from the request path to improve service stability. We also continue to monitor the deployment and validate service recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

14. monitoring Jul 15, 2026, 09:37 PM UTC

    Our investigation is ongoing, and we are actively validating multiple mitigation steps. We have identified inconsistent service startup behavior and are deploying configuration adjustments to improve application health while continuing to investigate the underlying trigger. We are monitoring the rollout and evaluating service recovery as the changes propagate. We'll provide an update in 60 minutes or sooner if additional information becomes available.

15. monitoring Jul 15, 2026, 10:53 PM UTC

    We've completed a deployment of the latest fix and are observing recovery as application instances continue returning to service. Our teams are validating that sufficient service capacity has been restored and are monitoring live traffic to confirm normal processing. We'll provide an update in 60 minutes or sooner if additional information becomes available.

16. monitoring Jul 16, 2026, 12:07 AM UTC

    We're continuing to investigate the service issue affecting Analytics customers in the US region. Our teams identified additional infrastructure constraints affecting service stability. We're now rolling back to a previous stable configuration version. We'll provide an update in 60 minutes or sooner if additional information becomes available.

17. monitoring Jul 16, 2026, 01:00 AM UTC

    We're continuing to work on restoring full-service stability for Analytics customers in the US region. We completed a rollback to a previous stable software version. Early results show improvement. We're now scaling additional capacity to further stabilize the service and are closely monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

18. monitoring Jul 16, 2026, 02:23 AM UTC

    Our investigation into the API Manager (APIM) ingestion functionality issue remains ongoing, and we have no new details to report at this time. We'll post our next update when a significant development occurs or as soon as more information becomes available.

19. monitoring Jul 16, 2026, 03:47 AM UTC

    We continue to investigate an issue affecting API Analytics services. Our teams have identified that delays are originating within the network layer rather than the application itself, and are working on a resolution. We're seeing signs of improvement and will provide the next update within 60 minutes, or as soon as more information is available.

20. monitoring Jul 16, 2026, 04:35 AM UTC

    We've applied the necessary configuration changes to address ‌service instability and are seeing signs of a gradual recovery with services and throughput. We'll continue to monitor service stability closely and provide the next update as soon as more information becomes available.

Read the full incident report →

Started Jul 15, 2026, 01:46 PM UTC· resolved Jul 15, 2026, 06:19 PM UTC

1. identified Jul 15, 2026, 01:46 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring Jul 15, 2026, 02:22 PM UTC

   We're aware of an issue impacting the MuleSoft EU production environment, causing intermittent errors. Users may experience deployment failures, errors when checking deployment status, and slow or degraded platform services. We're investigating the issue and will provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Jul 15, 2026, 03:25 PM UTC

   We've identified the trigger for this issue and are currently implementing measures to restore normal service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jul 15, 2026, 04:22 PM UTC

   We've completed a configuration change to remove a rate-limit bypass that was contributing to elevated authentication requests. We're continuing to execute additional measures to restore normal service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jul 15, 2026, 05:23 PM UTC

   We're continuing to execute additional measures to restore normal service, including rebalancing authentication service capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 14, 2026, 03:56 PM UTC· resolved Jul 14, 2026, 07:08 PM UTC

1. identified Jul 14, 2026, 03:56 PM UTC

   Degradation Started: agentforcePerformanceDegradation

2. monitoring Jul 14, 2026, 04:04 PM UTC

   We're aware of an issue affecting Agentforce Voice where users may experience intermittent failures when the voice agent doesn't capture or respond to input after the initial greeting, preventing completion of voice-based interactions. We identified the issue as being related to a connection failure between the voice service and its speech processing component. We're preparing a fix for deployment. We'll provide an update in 90 minutes or sooner if additional information becomes available.

3. monitoring Jul 14, 2026, 05:25 PM UTC

   A fix has been prepared and deployment is currently in progress for the impacted environments. We'll monitor service restoration and provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jul 14, 2026, 06:26 PM UTC

   We have deployed a fix and are monitoring service restoration; the early signals are positive. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 14, 2026, 10:43 AM UTC· resolved Jul 14, 2026, 06:49 PM UTC

1. identified Jul 14, 2026, 10:43 AM UTC

   Degradation Started: CCServiceDegradationManagedRuntime

2. monitoring Jul 14, 2026, 10:59 AM UTC

   We're investigating an issue preventing a subset of Commerce Cloud customers using Managed Runtime service from deploying or updating production and development sites. Customers may also encounter 504 errors in the Runtime Admin UI. Existing live storefronts remain unaffected. We’ve identified processing queue saturation as the likely trigger. A change to clear the impacted queue has been submitted for approval and is expected to be implemented shortly. Meanwhile, the team is evaluating a POD restart on the impacted environment as an additional mitigation. We'll provide another update in 30 minutes or sooner if new information becomes available.

3. monitoring Jul 14, 2026, 11:21 AM UTC

   We're proceeding with an action to clear the stuck queue tasks, which are preventing deployment requests from being processed. We'll validate whether this is successful in restoring service. Meanwhile, a service restart of the impacted environment remains available as a secondary option. We'll provide another update in 30 minutes or sooner if new information becomes available.

4. monitoring Jul 14, 2026, 11:49 AM UTC

   We've been unable to clear the stuck queue tasks. We're looking into clearing a subset of deployment jobs and analyzing metrics to see if this action is bringing about positive results. We’re also trying to better understand whether there were any recent changes which may have contributed to this issue. We'll provide another update in 30 minutes or sooner if new information becomes available.

5. monitoring Jul 14, 2026, 12:15 PM UTC

   The work to clear the deployment jobs hasn't provided the desired level of improvement. Further investigation pointed out that a recent deployment may be responsible for the high levels of traffic we're observing, which has resulted in the issue. We're in the process of determining possible resolution options. We'll provide another update in 30 minutes or sooner if new information becomes available.

6. monitoring Jul 14, 2026, 12:35 PM UTC

   The investigation has identified a recent platform release as the likely trigger, as it significantly increased the volume of deployment requests being processed leading to high levels of traffic. We’re now focused on reducing this load, and evaluating additional capacity and prioritization changes to restore normal deployment processing. We'll provide another update in 30 minutes or sooner if new information becomes available.

7. monitoring Jul 14, 2026, 01:13 PM UTC

   Further investigation has determined that this issue isn't a result of a recent release. Instead, certain deployment requests are repeatedly re-trying, significantly increasing the system load. Increased adoption of a recently introduced feature amplified this behavior, resulting in deployment requests accumulating faster than they can be processed. An emergency code fix is being developed, to bring customers out of impact. The fix will undergo testing and validation before being deployed to impacted instances, which is expected to take several hours. We'll provide another update in 3 hours or sooner if new information becomes available.

8. monitoring Jul 14, 2026, 02:37 PM UTC

   Investigations have highlighted that the impact radius is broader than initially understood and the start time was earlier than previously noted. We've added additional instances now and have a summary of the incident so far is as follows: Since 08:48 UTC, Commerce Cloud customers using the Managed Runtime service have been unable to deploy or update Storefronts, and may encounter 504 errors in the Runtime Admin UI. Existing live Storefronts remain unaffected. The investigation has determined that certain deployment requests are repeatedly re-trying, significantly increasing system load. Increased adoption of a recently introduced feature amplified this behavior, causing requests to accumulate faster than they can be processed. An emergency code fix is being developed and will undergo testing and validation before deployment to impacted instances, which is expected to take several hours. Steps are also underway to reduce system load in the interim. We'll provide another update in 3 hours or sooner if new information becomes available.

9. monitoring Jul 14, 2026, 04:37 PM UTC

   During investigations, we established that the level of impact differs from what was initially understood. We've updated the incident posting to reflect the current impact symptoms accurately. We've also deployed a configuration change to disable the feature driving the largest volume of deployment requests. This has significantly reduced the load on the system. We're monitoring recovery closely and will continue to process the backlog of deployment requests. We'll provide an update in 3 hours or sooner if additional information becomes available.

Read the full incident report →

Started Jul 13, 2026, 06:58 PM UTC· resolved Jul 13, 2026, 08:05 PM UTC

1. identified Jul 13, 2026, 06:58 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Jul 13, 2026, 07:06 PM UTC

   We're aware of an issue affecting Runtime Manager on Anypoint Management Center. Customers in the US region are unable to view their application list in the Runtime Manager UI. Customers can use the Command Line Interface (CLI) as a workaround to manage their applications while we investigate. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 13, 2026, 07:22 PM UTC

   We’ve implemented a solution to resolve the issue causing the feature degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 13, 2026, 10:56 AM UTC· resolved Jul 13, 2026, 01:44 PM UTC

1. identified Jul 13, 2026, 10:56 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Jul 13, 2026, 11:28 AM UTC

   We're investigating automation query delays where customers are experiencing longer than expected run times for individual queries or queries failing within Automation Studio. Multiple teams have been engaged to assist with the investigation. 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'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 13, 2026, 11:53 AM UTC

   We continue to investigate automation query delays and delays in task pickup within Automation Studio. Investigations indicate a capacity issue that's triggering these delays or failures. We're actively engaged in investigating the cause and we apologize for any inconvenience this issue is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 13, 2026, 12:16 PM UTC

   Customers continue to experience longer than expected run times or queries failing within Automation Studio. We're working on resolving the capacity issue and restoring normal operations. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 13, 2026, 12:53 PM UTC

   Remediation efforts are underway to resolve the delays and failures in query execution in Automation Studio. We apologize for any inconvenience this issue is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 13, 2026, 08:30 AM UTC· resolved Jul 13, 2026, 12:07 PM UTC

1. identified Jul 13, 2026, 08:30 AM UTC

   Degradation Started: tableauPerformanceDegradation

2. monitoring Jul 13, 2026, 08:52 AM UTC

   We’re investigating an issue impacting the Tableau Public site where customers may encounter a maintenance page, HTTP 502 errors, or request timeouts when attempting to access the site. The impact is currently limited to Tableau Public site. We’re investigating the cause of the issue and working to restore normal service. We've confirmed that the incident start time is earlier than initially reported and have updated this Trust post to reflect the correct start time. We will provide an update in 30 minutes or sooner if new information becomes available.

3. monitoring Jul 13, 2026, 10:00 AM UTC

   We continue to investigate the issue impacting the Tableau Public site. We've implemented few changes and are monitoring the service to evaluate their effectiveness. Although the site may load intermittently, published content and related services may remain unavailable. We will provide another update in 60 minutes or sooner if new information becomes available.

4. monitoring Jul 13, 2026, 11:18 AM UTC

   We're seeing improved service stability following the changes we've implemented and are continuing to monitor the service. While Tableau public site is accessible, some customers may still experience intermittent issues accessing published content and related services. We will provide another update in 60 minutes or sooner if new information becomes available.

Read the full incident report →

Started Jul 10, 2026, 04:11 PM UTC· resolved Jul 10, 2026, 09:39 PM UTC

1. identified Jul 10, 2026, 04:11 PM UTC

   Degradation Started: salesforceSpiffFeatureDegradation

Read the full incident report →

Started Jul 10, 2026, 03:52 AM UTC· resolved Jul 10, 2026, 07:49 AM UTC

1. identified Jul 10, 2026, 03:52 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jul 10, 2026, 04:16 AM UTC

   We're aware of an issue at the network tier impacting multiple production instances. Services affected include Einstein Activity Capture and Conversation Intelligence. Customers using these services may experience failures, errors, or delays. The issue is under active investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 10, 2026, 04:48 AM UTC

   We've identified an infrastructure configuration change as the trigger. We're rolling back that change and will complete the necessary validation and verification following the rollback. Our investigation has revealed that the impact is broader than initially understood, and the affected services now include Marketing Cloud Engagement. Additional instances have been identified as impacted, and customers on these instances will receive communications about this incident. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 10, 2026, 05:25 AM UTC

   Our investigation has confirmed that a subset of customers may experience issues with MuleSoft and Marketing Cloud Engagement services. We're continuing to roll back the infrastructure change that triggered the issue. We've successfully restored and validated one production environment, and we're now executing rollbacks in parallel across the remaining affected production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 10, 2026, 05:50 AM UTC

   Customers may experience delays or errors when accessing the affected services while the rollback is in progress. We're rolling back the infrastructure change across all affected production instances, and we're validating the instances where the rollback is already complete. We expect the rollback to be complete in approximately 90 minutes. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.

6. monitoring Jul 10, 2026, 06:43 AM UTC

   We have identified additional instances experiencing this issue, Customers on these newly identified instances will receive communications about this incident. Multiple regions have already recovered following the rollback action, and remediation continues on those remaining. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.

Read the full incident report →