Tableau Cloud Outage History

Started Sep 01, 2026, 01:56 PM UTC· resolved Sep 06, 2026, 07:16 PM UTC

1. identified Sep 01, 2026, 01:56 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 01, 2026, 02:02 PM UTC

   We're investigating an issue where a subset of B2B Commerce Cloud customers may find that the Standard Coupon Code component is not visible on the Cart page following the recent release. As a result, guest users may be unable to view or use the Standard Coupon Code component. The issue is currently limited to sandbox environments. We're working to identify the cause and determine a resolution. We'll provide an update in 30 minutes or sooner as more information becomes available.

3. monitoring Sep 01, 2026, 02:27 PM UTC

   We have identified a fix for the issue and are preparing it for testing. We'll validate the fix and work toward deploying it. We'll provide an update in 30 minutes or sooner as more information becomes available.

4. monitoring Sep 01, 2026, 02:58 PM UTC

   We're preparing a test environment that replicates the conditions of the impacted sandbox environment. Once the environment is ready, we'll validate the fix against the issue and proceed with the next steps toward deployment. We'll provide an update in 60 minutes or sooner as more information becomes available.

5. monitoring Sep 01, 2026, 03:46 PM UTC

   We're continuing to prepare and validate the fix for the issue affecting the Standard Coupon Code component in B2B Commerce Cloud sandbox environments. Once initial testing is complete, we'll progress the fix through additional validation before deployment. We'll provide an update in 3 hours or sooner as more information becomes available.

6. monitoring Sep 01, 2026, 06:49 PM UTC

   We've successfully validated the fix, which will be deployed via our regular release process. In the meantime, we are also developing a temporary workaround that affected customers can implement for immediate relief. In parallel, we're investigating whether the issue may affect additional environments beyond the sandbox environments initially identified and are assessing the appropriate remediation path. We'll provide another update as significant progress is made.

7. monitoring Sep 02, 2026, 08:27 AM UTC

   We're developing a Known Issue (KI) article with steps impacted customers can use to resolve the issue. The long-term fix will be included in our upcoming major release in mid October. Once the KI article is ready, we'll update this post with more details.

8. monitoring Sep 02, 2026, 11:44 AM UTC

   We've determined that the Known Issue (KI) article is no longer a viable workaround, since it requires a code change. We're revisiting the targeted fix we developed earlier and aim to deploy it soon. We'll share updates as development and testing progress. We'll provide an update as validation completes or when we have a significant update.

9. monitoring Sep 02, 2026, 06:58 PM UTC

   We're continuing to prepare the targeted fix for deployment. We encountered an intermittent issue during the release process that required us to retry part of the preparation, extending the deployment timeline. Release preparation is progressing again, and we've adjusted the rollout schedule accordingly. Once ready, we'll validate the fix in an initial environment before proceeding with the broader deployment. We'll provide another update as significant progress is made.

10. monitoring Sep 03, 2026, 05:27 AM UTC

    We've made progress on the Standard Coupon Code component issue within the Commerce Store in sandbox environments. As of 01:33 UTC, the fix is confirmed working on a subset of instances, and we’ve moved them on a separate trust post. Guest users on the remaining instances still can't apply coupon codes on the Cart page. We're developing and testing a fix for these instances. We'll provide an update within the next few hours or sooner as additional information is available.

11. monitoring Sep 04, 2026, 06:07 AM UTC

    We continue to work on resolving the issue where the standard coupon code component is not visible in B2B Commerce on Core, Developer and Sandbox environments. Since our last update, we have completed and verified testing of the fix for the store environments. The deployment of the fix is scheduled for the September 5, 2026, release window (18:00 UTC). We'll provide an update once the fix is deployed, or sooner if additional information becomes available.

12. monitoring Sep 06, 2026, 02:26 PM UTC

    We have verified a fix and begun deploying it across the impacted instances. We expect all environments to receive this update by September 7, 2026. We'll provide an update once the fix deployment is completed, or sooner if additional information becomes available.

Read the full incident report →

Started Sep 01, 2026, 10:36 AM UTC· resolved Sep 01, 2026, 07:25 PM UTC

1. identified Sep 01, 2026, 10:36 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 01, 2026, 10:36 AM UTC

   We’re investigating an issue affecting customers whose Record-Triggered Flows attempt to call an Agentforce agent is failing. This is impacting ‌all sandbox environments that received the recent release, and our investigation indicates that the release introduced a regression. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 01, 2026, 11:19 AM UTC

   We're pursuing an Emergency Release as a fix forward, and the release will be carried out in phases. 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 this ‌post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

4. monitoring Sep 01, 2026, 12:06 PM UTC

   We're continuing to prepare the Emergency Release with final checks underway. Once ready, the Emergency Release will be rolled out in phases to the impacted environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 01, 2026, 12:42 PM UTC

   We're continuing to prepare the Emergency Release and complete final checks. Once ready, the full deployment is expected to take several hours, as the Emergency Release will be rolled out in phases to the impacted environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Sep 01, 2026, 01:46 PM UTC

   We're continuing with the preparation for the Emergency Release and we remain on track with our final checks. Once deployed, the phased rollout to impacted environments is expected to take several hours to complete. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Sep 01, 2026, 02:51 PM UTC

   Preparing the Emergency Release and completing final checks continues. We have several steps to complete before we can begin deployment across the impacted sandboxes. We estimate the entire process will take several more hours to complete. Customers may still see errors when a Record-Triggered Flow calls an Agentforce agent until deployment completes. We'll provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring Sep 01, 2026, 03:50 PM UTC

   We’ve completed the build for the Emergency Release and are validating its effectiveness in resolving the issue. Once we have completed validation, we’ll begin deployment to impacted environments. We’ll provide another update in 2 hours or sooner if additional information becomes available.

9. monitoring Sep 01, 2026, 05:01 PM UTC

   We’ve successfully validated the Emergency Release in the initial environment, confirming that Record-Triggered Flows calling Agentforce agents are executing as expected without the previously observed errors. We’re now preparing to begin the phased rollout across the remaining impacted environments and will monitor progress as deployment proceeds. We’ll provide another update in 3 hours or sooner if additional information becomes available.

Read the full incident report →

Started Aug 30, 2026, 10:18 AM UTC· resolved Aug 31, 2026, 03:23 AM UTC

1. identified Aug 30, 2026, 10:18 AM UTC

   Disruption Started: ccCartsUnavailable

2. monitoring Aug 30, 2026, 10:23 AM UTC

   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.

3. monitoring Aug 30, 2026, 10:25 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 30, 2026, 11:03 AM UTC

   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.

5. monitoring Aug 30, 2026, 08:39 PM UTC

   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.

6. monitoring Aug 31, 2026, 12:26 AM UTC

   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.

7. monitoring Aug 31, 2026, 01:33 AM UTC

   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.

Read the full incident report →

Started Aug 27, 2026, 09:43 AM UTC· resolved Aug 27, 2026, 11:12 AM UTC

1. identified Aug 27, 2026, 09:43 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Aug 27, 2026, 09:57 AM UTC

   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.

3. monitoring Aug 27, 2026, 10:23 AM UTC

   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.

4. monitoring Aug 27, 2026, 10:58 AM UTC

   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.

Read the full incident report →

Started Aug 27, 2026, 09:25 AM UTC· resolved Aug 27, 2026, 10:15 AM UTC

1. identified Aug 27, 2026, 09:25 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Aug 27, 2026, 09:34 AM UTC

   We are investigating an issue affecting a subset of customers when trying to send SMS and email messages through our transactional messaging API. Some requests may intermittently fail with a server error, though retries are generally successful. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 25, 2026, 05:29 PM UTC· resolved Aug 25, 2026, 06:09 PM UTC

1. identified Aug 25, 2026, 05:29 PM UTC

   Degradation Started: muleSoftFeatureDisruption

2. monitoring Aug 25, 2026, 05:53 PM UTC

   We're addressing an issue that prevents some customers from publishing agent network assets through the Project View command line interface (CLI). We rolled back a recent change and have confirmed this has resolved the issue. We're continuing the rollback to the other impacted instances. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 25, 2026, 03:01 PM UTC· resolved Aug 25, 2026, 04:10 PM UTC

1. identified Aug 25, 2026, 03:01 PM UTC

   Degradation Started: herokuServiceDegradation

2. monitoring Aug 25, 2026, 03:40 PM UTC

   A recent security update for Common Runtime applications in the EU region may have unintentionally enforced a stricter policy for TLS certificates used for app default domain TLS termination (.herokuapp.com). This caused some clients to experience TLS handshake failures and to be unable to connect to apps. Engineers have identified the issue and we are working on remediating.

Read the full incident report →

Started Aug 24, 2026, 05:08 PM UTC· resolved Aug 26, 2026, 04:53 AM UTC

1. identified Aug 24, 2026, 05:08 PM UTC

   Degradation Started: salesforceSpiffFeatureDisruption

2. monitoring Aug 24, 2026, 05:27 PM UTC

   The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

3. monitoring Aug 24, 2026, 05:55 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

4. monitoring Aug 24, 2026, 06:30 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

5. monitoring Aug 24, 2026, 07:13 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

6. monitoring Aug 24, 2026, 07:42 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

7. monitoring Aug 24, 2026, 08:12 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

8. monitoring Aug 24, 2026, 08:31 PM UTC

   We have observed that the impact on service health has decreased from a disrupted to a degraded state. We have amended the posting to reflect this and have highlighted the approximate timings of this transition.

9. monitoring Aug 24, 2026, 09:01 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

10. monitoring Aug 24, 2026, 09:29 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

11. monitoring Aug 24, 2026, 10:01 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

12. monitoring Aug 24, 2026, 11:01 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

13. monitoring Aug 24, 2026, 11:35 PM UTC

    We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

14. monitoring Aug 25, 2026, 03:53 AM UTC

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

15. monitoring Aug 25, 2026, 02:24 PM UTC

    We are investigating a potential cause of the issue.

16. monitoring Aug 25, 2026, 02:56 PM UTC

    We’re investigating the cause of the issue and have engaged more engineers to help isolate the root cause. We will provide an update in 30 minutes or sooner if we have more information.

17. monitoring Aug 25, 2026, 04:26 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

18. monitoring Aug 25, 2026, 07:51 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

19. monitoring Aug 25, 2026, 09:34 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

20. monitoring Aug 25, 2026, 10:04 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

21. monitoring Aug 25, 2026, 10:56 PM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

22. monitoring Aug 26, 2026, 03:14 AM UTC

    The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

Read the full incident report →

Started Aug 21, 2026, 11:33 PM UTC· resolved Aug 22, 2026, 02:08 AM UTC

1. identified Aug 21, 2026, 11:33 PM UTC

   Degradation Started: intermittentLoginErrors

2. monitoring Aug 22, 2026, 12:30 AM UTC

   We continue to investigate performance degradation issue impacting EU54, EU55, CS333, and CS336. The next update will be provided in 60 minutes or sooner, if the situation warrants.

Read the full incident report →

Started Aug 20, 2026, 11:38 PM UTC· resolved Aug 21, 2026, 12:47 AM UTC

1. identified Aug 20, 2026, 11:38 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Aug 20, 2026, 11:38 PM UTC

   We are aware of an issue affecting the availability of certain services on instance CS246. Some customers may be unable to access affected services or may experience delays, timeouts or slow load times. Our technical teams are actively investigating the cause and working toward a resolution. We will provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 21, 2026, 12:01 AM UTC

   Upon further investigation, we believe this instance is now experiencing a service disruption as of 23:41 UTC, where users will have no access to Salesforce services hosted on the CS246 instance. We continue to actively work to fully understand the technical trigger. We will provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 21, 2026, 12:28 AM UTC

   We are preparing to undertake a site switch that is expected to be the quickest way for us to restore services for customers. We can’t currently indicate how long this will take at this stage, but we will provide an update as soon as we have more information. We will provide an update in 30 minutes or sooner if new information becomes available.

Read the full incident report →

Started Aug 20, 2026, 09:01 PM UTC· resolved Aug 24, 2026, 04:03 AM UTC

1. identified Aug 20, 2026, 09:01 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Aug 20, 2026, 09:09 PM UTC

   We're investigating an issue affecting Private Connect where some customers may experience degraded connectivity to Salesforce services. We've identified a recent change as the likely trigger and are working to deploy a fix. Additional teams have been engaged to help progress the remediation. We'll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Aug 20, 2026, 10:12 PM UTC

   We are continuing to develop and validate a fix for this issue before deploying it to the affected environments. We will provide another update as significant progress is made or sooner if additional information becomes available.

4. monitoring Aug 21, 2026, 01:59 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.

5. monitoring Aug 21, 2026, 02:17 AM UTC

   We’ve developed a fix for this issue and deployed it to test instances for validation before a wider rollout. Once validation is complete, we will deploy the fix to all impacted environments. We'll provide another update as significant progress is made or sooner if additional information becomes available.

6. monitoring Aug 21, 2026, 04:29 AM UTC

   We have successfully completed validation of the fix in our test environment and have begun rolling it out to production. Our teams will continue deploying the fix across all remaining impacted environments while closely monitoring services. We will provide another update as significant progress is made or sooner if additional information becomes available.

Read the full incident report →

Started Aug 20, 2026, 12:58 PM UTC· resolved Aug 20, 2026, 06:30 PM UTC

1. identified Aug 20, 2026, 12:58 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Aug 20, 2026, 01:00 PM UTC

   We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 20, 2026, 01:08 PM UTC

   We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 20, 2026, 01:30 PM UTC

   The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Aug 20, 2026, 01:53 PM UTC

   We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Aug 20, 2026, 02:06 PM UTC

   We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress. We've also 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’ll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Aug 20, 2026, 02:30 PM UTC

   We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Aug 20, 2026, 02:45 PM UTC

   The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Aug 20, 2026, 02:54 PM UTC

   Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Aug 20, 2026, 03:24 PM UTC

    We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. monitoring Aug 20, 2026, 03:51 PM UTC

    Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available.

12. monitoring Aug 20, 2026, 04:18 PM UTC

    Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding. We'll provide an update in 30 minutes or sooner if additional information becomes available.

13. monitoring Aug 20, 2026, 04:51 PM UTC

    We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

14. monitoring Aug 20, 2026, 05:26 PM UTC

    The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

15. monitoring Aug 20, 2026, 06:02 PM UTC

    We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect. We’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 19, 2026, 01:50 PM UTC· resolved Aug 19, 2026, 10:13 PM UTC

1. identified Aug 19, 2026, 01:50 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Aug 19, 2026, 02:07 PM UTC

   We're aware of an issue affecting MuleSoft sandbox environments in a subset of private spaces across the EU and US. Approximately 42 private spaces are currently degraded, blocking customer sandbox patching and pipeline deployments. Running applications and production environments aren't impacted. We've paused further patching to prevent additional impact and are actively investigating a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 19, 2026, 02:44 PM UTC

   We continue to investigate the MuleSoft sandbox patching issue affecting a subset of private spaces. One impacted space was recovered via a node restart, and we're validating this fix across all other impacted spaces. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

4. monitoring Aug 19, 2026, 02:59 PM UTC

   We continue to investigate the sandbox patching issue affecting Private Spaces. The impact radius has now increased to approximately 70 spaces across the EU and US. Node restarts proved ineffective and have been discontinued. We now believe a network configuration change in a recent platform release is the likely trigger. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

5. monitoring Aug 19, 2026, 03:50 PM UTC

   We continue to investigate the issue affecting sandbox patching and pipeline deployments in a subset of MuleSoft Private Spaces. Our teams are working with our third-party infrastructure provider to further investigate the network connectivity issues and determine the path to recovery. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

6. monitoring Aug 19, 2026, 04:58 PM UTC

   We identified the technical trigger as a third-party service limitation. We're working with our third-party infrastructure provider to implement changes needed to restore the affected environments and resume pending upgrades. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

7. monitoring Aug 19, 2026, 06:15 PM UTC

   We successfully validated a recovery method and are applying it to the remaining affected environments. In parallel, we're continuing to work with our third-party infrastructure provider to address the underlying service limitation and prevent additional impact. Running applications remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

8. monitoring Aug 19, 2026, 07:22 PM UTC

   We continue to apply the validated recovery method to affected MuleSoft Private Spaces, with environments returning to a healthy state as remediation progresses. We're also working with our third-party infrastructure provider to address the network-related issue and prevent additional impact. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available.

9. monitoring Aug 19, 2026, 08:54 PM UTC

   We continue to restore affected MuleSoft Private Spaces using the validated recovery method, with environments returning to a healthy state as remediation progresses. In parallel, we're also working with our third-party infrastructure provider on additional changes to prevent recurrence. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Aug 19, 2026, 06:07 AM UTC· resolved Aug 19, 2026, 07:33 AM UTC

1. identified Aug 19, 2026, 06:07 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Aug 19, 2026, 06:34 AM UTC

   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.

3. monitoring Aug 19, 2026, 06:36 AM UTC

   We're aware that some customers may be experiencing intermittent issues sending email. The issue was triggered during maintenance activity on our email infrastructure. We've identified the trigger and are actively working to restore full email send functionality. We'll provide another update within 30 minutes, or sooner if there's new information.

4. monitoring Aug 19, 2026, 07:01 AM UTC

   We've restored services on the impacted email infrastructure and we're validating email sending functionality before confirming full resolution. Some customers may continue to experience delivery delays during validation phase. We'll provide another update within 30 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Aug 18, 2026, 05:56 PM UTC· resolved Aug 18, 2026, 09:19 PM UTC

1. identified Aug 18, 2026, 05:56 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Aug 18, 2026, 06:26 PM UTC

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

3. monitoring Aug 18, 2026, 06:57 PM UTC

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

4. monitoring Aug 18, 2026, 07:34 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

5. monitoring Aug 18, 2026, 08:03 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

6. monitoring Aug 18, 2026, 08:36 PM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

Read the full incident report →

Started Aug 18, 2026, 09:51 AM UTC· resolved Aug 18, 2026, 04:46 PM UTC

1. identified Aug 18, 2026, 09:51 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Aug 18, 2026, 09:58 AM UTC

   We're investigating an issue impacting Data 360 provisioning in sandbox environments. Customers may experience failures when attempting to provision Data 360. Initial investigations indicate a recent configuration change that didn't complete successfully as the likely trigger. We're evaluating a rollback of that change in a test environment to confirm it resolves the failures. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 18, 2026, 10:07 AM UTC

   Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.

4. monitoring Aug 18, 2026, 10:48 AM UTC

   The rollback of the recent change is blocked because the build checks are repeatedly failing. We're engaging additional teams to work on alternate measures to resolve ‌build failures. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Aug 18, 2026, 11:08 AM UTC

   Customers may continue to experience failures when attempting to provision Data 360 in sandbox environments while we work on resolving the build failure blocking the rollback. The changes needed to revert the recent configuration are approved and in progress. In parallel, we've also identified ‌the last known good version to use as a fallback if needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Aug 18, 2026, 11:38 AM UTC

   We're continuing actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Aug 18, 2026, 12:06 PM UTC

   We're nearing completion of actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Aug 18, 2026, 12:41 PM UTC

   The most recent attempt to revert the configuration change didn't complete successfully and we're investigating a new strategy. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Aug 18, 2026, 01:10 PM UTC

   We're now pursuing an alternative fix, deploying an update with a corrected configuration. We'll provide an update on this in 60 minutes or sooner if additional information becomes available.

10. monitoring Aug 18, 2026, 02:16 PM UTC

    We continue working to resolve Data 360 provisioning failures in sandbox environments by deploying an update with a corrected configuration based on a previously stable version. We'll provide an update in 60 minutes or sooner if additional information becomes available.

11. monitoring Aug 18, 2026, 03:11 PM UTC

    We've begun deploying the corrected configuration and are validating the update before proceeding with a broader rollout. Customers may continue to experience Data 360 provisioning failures in sandbox environments while this work is underway. We'll provide an update in 90 minutes or sooner if additional information becomes available.

Read the full incident report →

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

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

   Degradation Started: featureServiceDisruption

2. monitoring Aug 17, 2026, 06:30 PM UTC

   We're investigating an issue affecting Proactive Monitoring limit alerts, where some customers may not receive expected notifications. The impact is limited to customers using the affected limit monitoring functionality, and the underlying Salesforce services remain available. We've narrowed the investigation to the processing of specific monitoring data used to generate these alerts and are working to restore normal alerting functionality. We'll provide another update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 17, 2026, 06:58 PM UTC

   We're continuing to investigate the issue affecting Proactive Monitoring limit alerts for a subset of customers. Our investigation confirms that other monitoring data continues to process normally, and the issue remains isolated to the specific monitoring data used to generate these limit alerts. We've validated the broader monitoring pipeline and are continuing to investigate why the affected limit-monitoring data is not being generated as expected. We'll provide another update in 60 minutes or sooner if additional information becomes available.

4. monitoring Aug 17, 2026, 07:35 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.

5. monitoring Aug 17, 2026, 07:40 PM UTC

   We performed a rolling restart on a test instance and have verified that Proactive Monitoring limit alerts have been successfully restored on that instance. We are now applying the same restart across the remaining affected instances. We'll provide another update once the rolling restarts have completed, or sooner if additional information becomes available.

Read the full incident report →

Started Aug 17, 2026, 03:55 PM UTC· resolved Aug 17, 2026, 05:58 PM UTC

1. identified Aug 17, 2026, 03:55 PM UTC

   Degradation Started: ccAccountManagerImpacted

2. monitoring Aug 17, 2026, 04:01 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.

3. monitoring Aug 17, 2026, 04:13 PM UTC

   We're investigating an issue affecting Account Manager where customers may experience intermittent errors. To restore service stability, we've initiated maintenance to transition Account Manager to a standby environment. During this activity, Account Manager will remain available in read-only mode, and customers may be unable to make configuration changes. We expect the maintenance activity to take approximately one hour and are closely monitoring progress. We'll provide an update in 90 minutes or sooner if additional information becomes available.

4. monitoring Aug 17, 2026, 05:36 PM UTC

   Our maintenance activity is progressing as planned. We've completed initial validation of the standby environment and are seeing expected service behavior. We are completing the remaining deployment activity and will then perform additional automated validation before transitioning traffic to the standby environment. We'll continue to monitor progress closely and provide another update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 17, 2026, 01:35 PM UTC· resolved Aug 17, 2026, 02:53 PM UTC

1. identified Aug 17, 2026, 01:35 PM UTC

   Disruption Started: ccStorefrontSAndOrBusinessManagerUnavailable

2. monitoring Aug 17, 2026, 01:46 PM UTC

   We’ve identified a service disruption which is intermittently affecting customers on POD248. Customers are intermittently unable to access their Storefronts and other Commerce Cloud services such as Business Manager. We're engaging additional teams to assist with the investigation. We're also evaluating whether a recent change is the trigger of this issue. 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’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 17, 2026, 02:01 PM UTC

   Upon further investigation, we’ve determined that customers may see 500 errors when trying to access their Commerce Cloud services, including Storefronts. Customers may be seeing signs of recovery, however, due to the intermittent nature of the issue we’re continuing the investigation. We’re analyzing error logs to better understand the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 17, 2026, 02:16 PM UTC

   Work is underway to understand whether a recent change resulted in the impact that customers are intermittently experiencing. In parallel, we're investigating if an issue affecting a network connection to a database is related. We’re working to gather relevant logs. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 16, 2026, 02:09 AM UTC· resolved Aug 18, 2026, 02:40 PM UTC

1. identified Aug 16, 2026, 02:09 AM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Aug 16, 2026, 02:19 AM UTC

   We are aware that some MuleSoft customers using Direct Connect connections in the EU region are experiencing connectivity issues reaching their internal networks. This is caused by an issue at a third-party vendor facility impacting Direct Connect connectivity. We will share the next update when the third-party vendor issue is remediated, or sooner, if there is any significant update.

3. monitoring Aug 17, 2026, 06:19 PM UTC

   Our third-party infrastructure provider continues remediation activities for the issue impacting Direct Connect connectivity in the EU region. We are seeing early signs of recovery as their restoration efforts progress, while work continues to restore the remaining affected infrastructure. We continue to monitor recovery and will provide another update as significant progress is made or sooner if additional information becomes available.

Read the full incident report →

Started Aug 14, 2026, 10:45 PM UTC· resolved Aug 15, 2026, 01:19 AM UTC

1. identified Aug 14, 2026, 10:45 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring Aug 14, 2026, 11:01 PM UTC

   We are currently investigating a performance degradation impacting the user interface for a subset of services in Mulesoft. Our teams are actively engaged and performing rollbacks to help mitigate the impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 14, 2026, 11:14 PM UTC

   We continue to investigate performance degradation impacting the user interface for a subset of services in Mulesoft. Our teams are actively engaged and performing rollbacks to help mitigate the impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 14, 2026, 11:50 PM UTC

   We are currently investigating a performance degradation impacting the user interface for a subset of services in Mulesoft. Rather than rolling back the change, we have decided to roll forward with a fix to resolve the issue more quickly. We are continuing to monitor for full recovery and will share a further update within 60 minutes or sooner if additional information becomes available.

5. monitoring Aug 15, 2026, 12:42 AM UTC

   We are currently investigating a performance degradation impacting the user interface for a subset of services in MuleSoft. Our initial roll-back attempt did not fully resolve the issue, so we moved to a roll forward approach and are building and testing an updated deployment. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 13, 2026, 11:42 AM UTC· resolved Aug 13, 2026, 01:42 PM UTC

1. identified Aug 13, 2026, 11:42 AM UTC

   Degradation Started: marketingCloudFeatureDegradation

2. monitoring Aug 13, 2026, 11:52 AM UTC

   We're aware that some users are experiencing errors when configuring (create/edit/update) SMS activities in Journey Builder. Ongoing automated SMS sends aren't affected. We're currently investigating and will provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 13, 2026, 12:21 PM UTC

   We continue to investigate errors preventing users from creating, editing, or updating SMS activities in Journey Builder. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 13, 2026, 12:49 PM UTC

   We attempted a redeployment of the Journey Builder app, which didn't resolve the issue, and are now investigating further. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 12, 2026, 07:06 PM UTC· resolved Aug 12, 2026, 11:17 PM UTC

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

   Degradation Started: performanceDegradation

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

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

3. monitoring Aug 12, 2026, 07:35 PM UTC

   We’re investigating a performance degradation impacting message queue delivery for some customers. Affected customers may experience asynchronous job delays at this time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Aug 12, 2026, 08:03 PM UTC

   Upon further investigating, we have determined that this issue is also impacting search indexes as well as some users' ability to log into their environments. We have identified the trigger and are taking action to help alleviate the impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Aug 12, 2026, 08:25 PM UTC

   Upon further investigation, we have determined that this issue is also impacting Global search. We are looking into additional actions to help alleviate the impact, including the possibility of increasing database capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring Aug 12, 2026, 09:24 PM UTC

   We are continuing to investigate the trigger for this incident as our previous mitigation efforts have not resolved the issue as expected. We have engaged additional teams and are continuing to evaluate the possibility of increasing database capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Aug 12, 2026, 10:27 PM UTC

   We are continuing to work on a possible resolution for this incident. Our investigation has traced the trigger to a gradual rise in login traffic that has been ongoing for a few days. We are now reviewing recent account level changes that may be contributing to this pattern. Our mitigation efforts have relieved some database CPU load, but the login traffic remains high. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 11, 2026, 09:24 AM UTC· resolved Aug 11, 2026, 11:27 AM UTC

1. identified Aug 11, 2026, 09:24 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Aug 11, 2026, 09:26 AM UTC

   We’re investigating an issue where Managed Runtime customers are unable to access any of the Commerce Cloud services. We’ve identified a recent change as the trigger for this issue and are actively rolling back the change. We’ll provide another update in 30 minutes or sooner if additional information

3. monitoring Aug 11, 2026, 09:57 AM UTC

   We are proceeding with a region switch to establish a full replica of the environment in another region. As part of this process, Account Manager has been placed in maintenance mode and is currently read-only. Any changes made in Account Manager during this period will not be saved. The region switch is expected to take some time to complete. Once completed, we will validate traffic flow and confirm that all services are operating as expected. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

4. monitoring Aug 11, 2026, 11:00 AM UTC

   The region switch is taking more time than anticipated but is progressing well. Initial tests on the standby environment have given positive results. During this maintenance period, Commerce Cloud On-Demand sandboxes cannot be created, started, or restarted . On-Demand sandboxes that were already running before the maintenance began are not affected. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Aug 10, 2026, 03:25 PM UTC· resolved Aug 10, 2026, 03:46 PM UTC

1. identified Aug 10, 2026, 03:25 PM UTC

   Degradation Started: herokuFeatureDegradation

Read the full incident report →