Salesforce Outage History

Started Oct 23, 2026, 04:24 PM UTC· resolved Oct 23, 2026, 05:41 PM UTC

1. identified Oct 23, 2026, 04:24 PM UTC

   Degradation Started: muleSoftFeatureDisruption

2. monitoring Oct 23, 2026, 04:59 PM UTC

   We're aware of an issue affecting Runtime Manager in the Government Cloud environment. Schedules for some customers are running about 7 hours later than configured. The issue is linked to a time zone setting on the affected servers. We have corrected the time zone settings and are restarting the affected servers. We're monitoring to confirm schedules return to their configured times and will provide an update in 60 minutes or as more information becomes available.

Read the full incident report →

Started Oct 23, 2026, 02:35 AM UTC· resolved Oct 23, 2026, 08:45 AM UTC

1. identified Oct 23, 2026, 02:35 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Oct 23, 2026, 02:51 AM UTC

   We've confirmed that affected users can't log in to their org and see an error message. We began restarting our servers in stages to restore access. We're continuing to investigate the cause. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

3. monitoring Oct 23, 2026, 03:08 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 Oct 23, 2026, 03:18 AM UTC

   Affected users can't log in, and attempts to open orgs return an internal server error. We're continuing to investigate the trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Oct 23, 2026, 03:35 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.

6. monitoring Oct 23, 2026, 03:49 AM UTC

   We’ve identified a mismatch between a recent application update and a database change, stopping users from logging in. We’re planning to roll back the update across impacted instances. We’re also preparing to test a newer version on one of impacted instance to validate whether it restores user access. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Oct 23, 2026, 04:03 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.

8. monitoring Oct 23, 2026, 04:18 AM UTC

   We confirmed that we restored access on one impacted instance by rolling back a recent application update. At 03:57 UTC, we began deploying a newer version to a second impacted instance to validate the fix. Once validation is complete, we plan to roll out the fix to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We’ll provide the next update within 30 minutes, or sooner if new information becomes available.

9. monitoring Oct 23, 2026, 04:41 AM UTC

   We confirmed that a fix forward has restored access on the second impacted instance USA1072 at 04:11 UTC. We're now preparing to deploy this fix forward to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We'll post a separate Trust update for each instance that receives the fix, so each shows an accurate end time We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Oct 23, 2026, 05:08 AM UTC

    We have identified the fix-forward deployment as our path to full recovery and are expediting its rollout across all remaining impacted instances. Deployment is currently underway across multiple instances, and we do not yet have an estimated time for completion. Users on instances that have not received the updated version may continue to experience issues logging in or accessing their orgs. We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available.

11. monitoring Oct 23, 2026, 05:34 AM UTC

    We continue to prioritize restoring access across all remaining impacted instances. We are actively deploying the identified fix across multiple instances, with the fix-forward deployment remaining our path to full recovery. The rollout is still in progress, and we are closely monitoring deployment progress and validating recovery as each instance receives the updated version. While we are working to complete the rollout as quickly as possible, we do not yet have an estimated time for full recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs .We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available.

12. monitoring Oct 23, 2026, 06:01 AM UTC

    The fix-forward deployment is progressing well across the remaining impacted instances, and our teams continue to prioritize restoring access as quickly as possible. We are closely monitoring the rollout and validating recovery as each instance receives the updated version. We have removed recovered instances from the main incident post to accurately reflect their respective impact end times. We will continue to provide instance-specific recovery updates as deployment progresses. Users on instances that have not yet received the fix may continue to experience issues logging in or accessing their orgs. While deployment is progressing, we do not yet have an estimated time for full recovery. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

13. monitoring Oct 23, 2026, 06:13 AM UTC

    Our investigation has confirmed that the scope of impact is narrower than initially identified. We have verified that instance USA594 was not affected by this incident and have removed it from the list of impacted instances. As a result, this instance will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance.

14. monitoring Oct 23, 2026, 06:26 AM UTC

    We continue to make steady progress with the fix-forward deployment across the remaining impacted instances. Our teams are actively rolling out the fix-forward and verifying that users can successfully log in and access their orgs as each instance recovers. As we confirm recovery, we are removing the affected instances from the main incident post to accurately reflect their respective impact end times. We will continue to share instance-specific updates as we validate recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. Although the deployment is progressing as expected, we do not yet have an estimated time for full recovery. Restoring access across all remaining impacted instances remains our highest priority. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

15. monitoring Oct 23, 2026, 06:54 AM UTC

    The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances and validating that users can successfully log in and access their orgs. As we confirm recovery, we continue to update the incident scope and remove recovered instances from the main incident post to accurately reflect their respective impact end times. We will communicate recovery through instance-specific updates. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

16. monitoring Oct 23, 2026, 07:16 AM UTC

    We have verified that instances IND116, USA326, USA938s, and USA1230 were not affected by this incident and have removed it from the list of impacted instances. As a result, these instances will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance.

17. monitoring Oct 23, 2026, 07:35 AM UTC

    The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances. We're continuing to provide recovery confirmation and accurate resolved timestamps for instances via separate postings. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

18. monitoring Oct 23, 2026, 08:09 AM UTC

    The fix-forward deployment continues to progress across the remaining instances. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

19. monitoring Oct 23, 2026, 08:38 AM UTC

    The fix-forward deployment continues to progress across the remaining instance. Users on instance awaiting the fix may continue to experience issues logging in or accessing their orgs. We will provide our next update in 30 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Oct 21, 2026, 02:57 AM UTC· resolved Oct 21, 2026, 03:34 AM UTC

1. identified Oct 21, 2026, 02:57 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Oct 21, 2026, 03:11 AM UTC

   We're aware of an issue impacting Agentforce Coworker. A subset of customers may experience intermittent request failures, and conversations may stop partway through an answer without an error message. We engaged the third-party service provider, and we're seeing error rates decrease. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Oct 20, 2026, 10:28 AM UTC· resolved Oct 20, 2026, 11:03 AM UTC

1. identified Oct 20, 2026, 10:28 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Oct 20, 2026, 10:40 AM UTC

   We're investigating a login issue where customers aren't receiving any outbound emails, including password reset emails and one-time passcodes (OTPs). This is preventing logins. We've identified a recent change to an email service component as the likely trigger. We're reverting the change to restore email delivery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Oct 19, 2026, 08:24 PM UTC· resolved Oct 19, 2026, 09:42 PM UTC

1. identified Oct 19, 2026, 08:24 PM UTC

   Degradation Started: featureServiceDisruption

Read the full incident report →

Started Oct 19, 2026, 12:31 PM UTC· resolved Oct 20, 2026, 01:08 AM UTC

1. identified Oct 19, 2026, 12:31 PM UTC

   Degradation Started: salesforceDataCloudFeatureDegradation

2. monitoring Oct 19, 2026, 01:39 PM UTC

   Data 360 customers are experiencing activation jobs are queued and are timing out. A subset of customers using Marketing Cloud Connector are seeing the issue as well. We have identified that the issue is a result of a third-party provider issue. We’re working alongside the third-party provider to find a resolution to this issue. We’re also evaluating a switch to alternative infrastructure to restore processing sooner. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Oct 19, 2026, 01:53 PM UTC

   We're still investigating whether we can take any action on our side to restore service for affected customers. The third-party provider has confirmed it has the right resources in place and is continuing to work on a resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Oct 19, 2026, 02:08 PM UTC

   Following further investigation, we've identified additionally impacted customers and customers in these instances will receive communications related to this incident going forward. We've also determined that these features may be experiencing the same issue: Calculated Insights and Data Transform. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Oct 19, 2026, 02:31 PM UTC

   We're in the process of testing whether we can switch to an alternative infrastructure to restore the processing of activation jobs. The third-party service provider is also continuing to work to resolve the issue on their end. We've also identified additionally impacted customers and customers in these instances will receive communications related to this incident going forward. We’ve also determined that customers using Data 360 CRM Connectors may be seeing impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Oct 19, 2026, 02:52 PM UTC

   We're testing a switch to alternative infrastructure to restore processing of activation jobs, and we're seeing positive results. We're working to apply this change across the impacted features and will continue to monitor progress. We remain in contact with the third-party service provider responsible for this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Oct 19, 2026, 03:17 PM UTC

   We've identified the trigger of this issue with a third-party provider and they are rolling back a recent change. An estimated timeline for completing the rollback is currently unavailable. In parallel, we're validating a fallback that sends affected jobs through another processing path. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Oct 19, 2026, 03:46 PM UTC

   We're still waiting on our third-party provider to finish rolling back the change that triggered this issue, and we don't yet have a completion time. In the meantime, we've moved some affected services to another processing path and confirmed that new jobs are running successfully in a test environment. We're applying the same change to more instances, and we'll then move on to the live environment. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Oct 19, 2026, 04:12 PM UTC

   Our third-party provider has confirmed that recovery is underway and that jobs are processing again. We're seeing more jobs complete successfully on affected instances. We're still waiting for the provider to confirm that its actions are complete. We moved some affected services to another processing path, and new jobs on those services are running successfully. We continue to monitor recovery. We're also working to determine whether jobs that were pending will process on their own or need to be resubmitted. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Oct 19, 2026, 04:43 PM UTC

    Our third-party provider is processing new jobs successfully on affected instances. The provider identified an issue that is slowing older pending jobs. It's deploying a fix to resolve. Customers may continue to see delayed Calculated Insights, Data Transforms, activation files, and data ingestion jobs until the backlog clears. We're reviewing each service to decide whether to wait for older jobs or cancel and resubmit them. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. monitoring Oct 19, 2026, 05:10 PM UTC

    Our third-party provider is deploying a fix for older pending jobs and expects to clear that backlog within about four to five hours. We moved data ingestion to another processing path, and new data ingestion jobs are now completing. Data ingestion jobs submitted before that change are still pending. We haven't canceled any pending jobs, and we're assessing the safest way to recover them without additional impact.Customers may continue to see delayed activation files, Calculated Insights, Data Transforms, and data ingestion jobs. We'll provide an update in 30 minutes or sooner if additional information becomes available.

12. monitoring Oct 19, 2026, 05:36 PM UTC

    Most affected services are now processing new jobs successfully. Services that moved to another processing path, including activations, data services, and insights, are completing new jobs. We're confirming recovery for the remaining services. Jobs that were pending before the recovery are still delayed. Our third-party provider expects to clear them within four hours. We're working with the provider on the safest way to recover these older jobs and avoid additional impact. Customers may continue to see delayed activation files, Calculated Insights, Data Transforms, and data ingestion jobs. We'll provide an update in 30 minutes or sooner if additional information becomes available.

13. monitoring Oct 19, 2026, 06:05 PM UTC

    Before our third-party provider can handle older queued jobs, the provider needs to finish deploying its fix. Once the fix is complete, many of those older jobs will fail. We'll retry them automatically where possible. Customers may see failed or delayed activation files, Calculated Insights, Data Transforms, and data ingestion jobs during this time. Some jobs may need to be rerun. We're reviewing each service to confirm retries work as expected. We'll provide an update in 30 minutes or sooner if additional information becomes available.

14. monitoring Oct 19, 2026, 06:34 PM UTC

    Our third-party provider is still deploying a fix for older pending jobs and expects to clear that backlog within three hours. When the fix finishes, many of those older jobs may fail. We'll retry them automatically where possible. Customers may see failed or delayed activation files, Calculated Insights, Data Transforms, and data ingestion jobs during this time. We're reviewing each service to confirm how it will handle these jobs. We'll provide an update in 60 minutes or sooner if additional information becomes available.

15. monitoring Oct 19, 2026, 07:41 PM UTC

    Our third-party provider’s deployment to fix older pending jobs is still in progress and is expected to complete within approximately 4 hours. In the meantime, we are continuing to evaluate alternate ways to safely retry and reprocess jobs in parallel to expedite mitigation. Customers may continue to see failed or delayed activation files, Calculated Insights, Data Transforms, and data ingestion jobs during the recovery process. We'll confirm the retry approach for each service as soon as it's validated. We appreciate your patience and will share another update as soon as there's significant progress.

16. monitoring Oct 19, 2026, 08:25 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.

17. monitoring Oct 19, 2026, 08:42 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.

18. monitoring Oct 19, 2026, 10:50 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.

19. monitoring Oct 19, 2026, 11:43 PM UTC

    Our third-party provider continues to process the backlog of pending jobs, which is progressing well and has been decreasing steadily. We're nearing completion of the backlog. A number of pending jobs may still require additional time to complete, so a subset of customers may continue to see failed or delayed activation files and related data jobs. We'll provide an update once we can clarify this further or once additional information becomes available.

Read the full incident report →

Started Oct 19, 2026, 01:45 AM UTC· resolved Oct 19, 2026, 05:55 AM UTC

1. identified Oct 19, 2026, 01:45 AM UTC

   Degradation Started: salesforceOrderManagementFeatureDegradation

2. monitoring Oct 19, 2026, 02:18 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’ll provide an update once the fix is deployed, or sooner if additional information becomes available.

Read the full incident report →

Started Oct 16, 2026, 08:30 PM UTC· resolved Oct 17, 2026, 10:09 AM UTC

1. identified Oct 16, 2026, 08:30 PM UTC

   Degradation Started: tableauFeatureDegradation

2. monitoring Oct 16, 2026, 08:47 PM UTC

   We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Customers using extract-based data sources may see calculated fields renamed. Workbooks and dashboards that depend on those fields may not display correctly. As a workaround, customers can switch to a live connection. A Known Issue article is available with additional details here: https://help.salesforce.com/s/issue?id=a02g700000BteHp We are actively working on a fix and redeployment to mitigate this issue. We will provide an update as soon as more information becomes available.

3. monitoring Oct 17, 2026, 04:29 AM UTC

   We have successfully validated and tested the fix in a lower environment. Initial reports have indicated positive results, and we are working to roll out the fix to the remaining production instances. We will provide an update as soon as more information becomes available.

Read the full incident report →

Started Oct 16, 2026, 01:48 PM UTC· resolved Oct 16, 2026, 02:48 PM UTC

1. identified Oct 16, 2026, 01:48 PM UTC

   Degradation Started: performanceDegradationAsynchronousProcessing

Read the full incident report →

Started Oct 15, 2026, 07:33 AM UTC· resolved Oct 15, 2026, 07:54 AM UTC

1. identified Oct 15, 2026, 07:33 AM UTC

   Degradation Started: performanceDegradation

Read the full incident report →

Started Oct 15, 2026, 06:34 AM UTC· resolved Oct 16, 2026, 11:02 PM UTC

1. identified Oct 15, 2026, 06:34 AM UTC

   Degradation Started: tableauFeatureDegradation

2. monitoring Oct 15, 2026, 06:38 AM UTC

   We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Affected customers may experience dashboards and workbooks failing to load, remaining stuck on "Loading data sources," or taking longer than expected to open. To reduce the impact, we disabled a related feature, and we're working on a fix. We don't have an estimated time for resolution yet and we'll provide an update as additional information becomes available.

3. monitoring Oct 15, 2026, 09:19 AM UTC

   We’ve identified a likely cause related to a recent change that may be causing processes to become deadlocked while loading data sources. We’re working on a code fix to address the suspected cause. Once ready, we’ll test the fix in lower environments before proceeding with production deployment. The previously implemented mitigation of disabling a related feature remains in place to help reduce customer impact. We don’t have an estimated time for resolution yet. We’ll provide another update if additional information becomes available.

4. monitoring Oct 15, 2026, 04:42 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 Oct 15, 2026, 09:28 PM UTC

   We have validated the fix and are working towards production rollout. The earlier mitigation, which disabled a related feature, remains in effect to limit customer impact. There's no estimated resolution time at this point. We'll share another update when more information is available.

6. monitoring Oct 16, 2026, 01:46 AM UTC

   We've deployed the fix to several instances, and early results are positive. We haven't seen data sources stall when loading in those instances. Deployment to the remaining instances is scheduled for off-peak hours. Customers on instances still awaiting the fix may continue to see data sources stall when loading. We don't have a resolution time yet. We'll provide an update when more information is available.

7. monitoring Oct 16, 2026, 05:55 AM UTC

   As the fix deployment completes in each region and we restore services, we'll move the resolved instances to a separate Trust post so each resolution time is clear.

Read the full incident report →

Started Oct 14, 2026, 06:53 PM UTC· resolved Oct 14, 2026, 07:21 PM UTC

1. identified Oct 14, 2026, 06:53 PM UTC

   Disruption Started: serviceDisruption

2. monitoring Oct 14, 2026, 06:53 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.

Read the full incident report →

Started Oct 13, 2026, 04:58 PM UTC· resolved Oct 13, 2026, 06:43 PM UTC

1. identified Oct 13, 2026, 04:58 PM UTC

   Disruption Started: tableauServiceDisruption

2. monitoring Oct 13, 2026, 05:45 PM UTC

   We’re investigating the cause of the issue. We will provide an update once we have more information.

Read the full incident report →

Started Oct 13, 2026, 08:05 AM UTC· resolved Oct 13, 2026, 08:42 AM UTC

1. identified Oct 13, 2026, 08:05 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Oct 13, 2026, 08:12 AM UTC

   We're aware of an issue impacting Data 360 data share. As a result, customers can't access shared data through external data warehouse integrations, and requests from connectors are failing. Older versions of connectors aren't impacted. We've started rolling back a recent change to restore access, and we're monitoring progress. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Oct 13, 2026, 08:18 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.

Read the full incident report →

Started Oct 09, 2026, 11:24 PM UTC· resolved Oct 09, 2026, 11:49 PM UTC

1. identified Oct 09, 2026, 11:24 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Oct 09, 2026, 11:27 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.

Read the full incident report →

Started Oct 08, 2026, 05:59 PM UTC· resolved Oct 08, 2026, 10:31 PM UTC

1. identified Oct 08, 2026, 05:59 PM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Oct 08, 2026, 06:09 PM UTC

   We’re investigating an issue affecting CRM Analytics recipe execution for a subset of customers. Affected customers may be unable to run their recipes. The issue is limited to certain Salesforce-hosted environments, and Hyperforce environments are not affected. We’ve identified that a required processing component is unavailable in some affected environments following a recent deployment. We’re working to restore the component and resume normal recipe execution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Oct 08, 2026, 06:29 PM UTC

   We're continuing to investigate the issue affecting CRM Analytics recipe runs for a subset of customers. Our teams identified a potential fix and are currently testing it on a limited scope before rolling it out further. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Oct 08, 2026, 06:42 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 Oct 08, 2026, 06:42 PM 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.

6. monitoring Oct 08, 2026, 07:01 PM UTC

   We're testing a rollback of a recent change on a limited scope to confirm it resolves the issue affecting CRM Analytics recipe runs. Once validated, we'll assess rolling the fix out further. We'll provide an update upon completion of the initial deployment or sooner if additional information becomes available.

7. monitoring Oct 08, 2026, 09:28 PM UTC

   Rollback testing was successful, and we are now proceeding to apply this rollback change across the remaining affected environments. Additionally, 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. We'll provide an update upon completion of the deployment or sooner if additional information becomes available.

Read the full incident report →

Started Oct 08, 2026, 02:00 PM UTC· resolved Oct 08, 2026, 03:58 PM UTC

1. identified Oct 08, 2026, 02:00 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Oct 08, 2026, 02:31 PM UTC

   We've identified that new servers are failing to start because required startup files are missing. As a result, we can't add the capacity needed to handle customer traffic, and some customers may experience slow responses or errors. We're reviewing settings and testing fixes on the affected servers. We'll provide an update in 30 minutes, or sooner if we have more information.

3. monitoring Oct 08, 2026, 02:48 PM UTC

   We've tested a fix to restore a missing configuration setting on new servers and are preparing to apply it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Oct 08, 2026, 02:55 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 Oct 08, 2026, 03:24 PM UTC

   We've applied a fix to add a missing configuration setting to affected servers and are restarting them to restore full capacity. Customers may experience a brief increase in background system activity as servers restart. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Oct 07, 2026, 06:35 AM UTC· resolved Oct 07, 2026, 11:17 AM UTC

1. identified Oct 07, 2026, 06:35 AM UTC

   Degradation Started: muleSoftFeatureDisruption

2. monitoring Oct 07, 2026, 06:45 AM UTC

   We're investigating a Salesforce feature disruption affecting MuleSoft Government Cloud customers following a planned maintenance. Customers may see errors managing APIs in API Manager, and they cannot publish assets in Exchange. Runtime Manager and Anypoint Monitoring may not send alerts. We're working to complete the remaining maintenance steps to restore services. We'll provide an update as more information becomes available.

Read the full incident report →

Started Oct 06, 2026, 04:56 PM UTC· resolved Oct 06, 2026, 06:51 PM UTC

1. identified Oct 06, 2026, 04:56 PM UTC

   Degradation Started: tableauFeatureDegradation

2. monitoring Oct 06, 2026, 04:56 PM UTC

   Some Tableau users may be unable to view projects if they are not a creator or administrator.

3. monitoring Oct 06, 2026, 05:27 PM UTC

   We're continuing to investigate limited project visibility affecting some Tableau Cloud users without Creator or Administrator roles. We've attempted a feature flag change to help restore visibility. If that doesn't resolve the issue, we'll roll back to the previous version. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Oct 06, 2026, 06:17 PM UTC

   The configuration change we implemented did not resolve the issue affecting some Tableau Cloud users who can't view their assigned projects. We've begun rolling back the recent platform update we believe to have introduced this issue and are closely monitoring the rollback's progress. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Oct 05, 2026, 10:02 AM UTC· resolved Oct 05, 2026, 10:26 AM UTC

1. identified Oct 05, 2026, 10:02 AM UTC

   Degradation Started: marketingCloudFeatureDegradation

Read the full incident report →

Started Oct 04, 2026, 01:07 PM UTC· resolved Oct 05, 2026, 01:02 AM UTC

1. identified Oct 04, 2026, 01:07 PM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Oct 04, 2026, 01:31 PM UTC

   At 11:15 UTC on October 4, 2026, a feature disruption began impacting CRM Analytics in the production environment. As a result, customers in the affected environment are unable to use CRM Analytics, and their CRM Analytics jobs are failing. We are investigating the issue and analyzing data to determine the best path to resolution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Oct 04, 2026, 02:01 PM UTC

   We have identified an issue related to high memory utilization due to an underlying service. We are exploring multiple paths to isolate the underlying cause of the issue and implement a fix to restore the services. We are reviewing the error logs and diagnostic information. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Oct 04, 2026, 02:30 PM UTC

   We remain engaged and will continue to determine the best path to resolution. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Oct 04, 2026, 03:22 PM UTC

   We have identified a potential trigger of the issue and are reviewing additional logs. In parallel, we are working on allocating additional resources to accommodate for increased memory utilization as an interim fix. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring Oct 04, 2026, 04:45 PM UTC

   We're continuing to work on restoring service for CRM Analytics customers on the affected instances. Our investigation found that a supporting service used during startup is slow to respond. We've applied configuration changes and are raising a request limit on that service. We'll provide the next update once additional information becomes available.

7. monitoring Oct 04, 2026, 06:09 PM UTC

   We continue to work on mitigation to restore service for CRM Analytics customers. Some customers may still see failures or delays when running recipes. We'll provide an update once additional information becomes available.

8. monitoring Oct 04, 2026, 08:06 PM UTC

   We continue to work on mitigation to restore service for CRM Analytics customers. Some customers may still see failures or delays when running recipes. We're working with other teams to identify the source of the increased load. We'll provide an update after additional information becomes available.

9. monitoring Oct 04, 2026, 10:23 PM UTC

   We continue to work on mitigation to restore service for CRM Analytics customers. We're taking steps to reduce the load on the affected service. Some customers may still see failures or delays. We'll provide an update after additional information becomes available.

10. monitoring Oct 04, 2026, 10:36 PM UTC

    We've identified that Data Cloud customers are also affected. Some Data Cloud ingestion and segmentation tasks may fail or be delayed, in addition to CRM Analytics recipe runs. We continue to work on mitigation to restore service for both. We'll provide an update once additional information becomes available.

11. monitoring Oct 05, 2026, 12:16 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.

12. monitoring Oct 05, 2026, 12:34 AM UTC

    We've completed the recovery steps on the affected internal services. CRM Analytics recipe runs are starting to succeed, and we're monitoring to confirm full recovery. Additionally, we're working to restore Data 360 segmentation tasks. We’ll provide an update as additional information becomes available.

Read the full incident report →

Started Oct 01, 2026, 10:06 PM UTC· resolved Oct 02, 2026, 04:58 PM UTC

1. identified Oct 01, 2026, 10:06 PM UTC

   Degradation Started: govCloudPerformanceDegradationThirdPartyInfrastructureProviderIssueInitial

2. monitoring Oct 01, 2026, 10:19 PM UTC

   We’re aware of an issue affecting .mil network connectivity to some Salesforce GovCloud environments. Customers using affected network paths may be unable to access Salesforce services or may experience intermittent connectivity. We’ve engaged the global infrastructure provider for a subset of government agencies to investigate the issue further and are monitoring for recovery. We’ll provide another update when there is a significant development.

Read the full incident report →

Started Sep 29, 2026, 05:38 AM UTC· resolved Sep 29, 2026, 08:01 AM UTC

1. identified Sep 29, 2026, 05:38 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 29, 2026, 06:31 AM UTC

   We’re aware of an issue affecting Log Center on a subset of PODs, where customers may experience missing application, deployment, and Ecom logs. The impact began at 02:36 UTC and may affect log monitoring, alerting, and third-party log streaming. We are actively investigating the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 29, 2026, 07:00 AM UTC

   We’ve confirmed that the log processing service is operating normally and that a recent planned application update is not related to the issue. Our teams are restarting the affected log collection component to restore full log visibility, beginning with one impacted instance. We’ll continue to monitor recovery and provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 29, 2026, 07:35 AM UTC

   We’ve restarted the affected log collection components and confirmed that log activity has returned to normal on those instances. We identified an additional impacted instance, completed the restart, and confirmed recovery there as well. We’re continuing to review other instances flagged by monitoring and will restart and validate them as needed. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 29, 2026, 02:46 AM UTC· resolved Sep 29, 2026, 03:07 AM UTC

1. identified Sep 29, 2026, 02:46 AM UTC

   Degradation Started: muleSoftFeatureDisruption

Read the full incident report →

Started Sep 28, 2026, 09:14 AM UTC· resolved Sep 28, 2026, 10:34 AM UTC

1. identified Sep 28, 2026, 09:14 AM UTC

   Disruption Started: muleSoftServiceDisruption

2. monitoring Sep 28, 2026, 09:24 AM UTC

   We're investigating SSO login failures where customers logging in via single sign-on (SSO), specifically to Anypoint Platform, are unable to authenticate. The impact spans the platform for anyone using SSO login. We've identified a recent change that's preventing customers whose org's stored Identity Provider (IDP) signing certificate isn't formatted as Privacy-Enhanced Mail (PEM) from logging into access management. Users who are already logged in are unaffected and won't lose access or experience disruptions. We're executing a rollback to resolve the ongoing login issues. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 28, 2026, 09:57 AM UTC

   We're continuing to work on a rollback to resolve the single sign-on (SSO) login issue impacting Anypoint Platform. The rollback is in progress for one of the regions and we're checking to see if this resolves the issue. Users who are already logged in are unaffected and won't lose access or experience disruptions. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Sep 28, 2026, 10:18 AM UTC

   The rollback in the US region is complete without any errors. The rollback is in progress for the remaining impacted regions and should be completed within 60 minutes. Users who are already logged in, continue to remain unaffected and won't lose access or experience any disruptions. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →