Salesforce

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-10-21 18:58 UTC

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

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Agentforce, coreService

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-21 03:11 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...

2. startTimeRevision 2026-10-21 03:25 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...

3. update 2026-10-21 03:30 UTC

   Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services. We apologize for how this incident affected you and your business. We will...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Agentforce

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-20 17:23 UTC

   During this time Agentforce Coworker may have been unresponsive for some customers. The issue was linked to reduced availability of a third-party service that Coworker relies on. That service has recovered, and Agentforce Coworker is now operating normally. We apologize for how...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: MarketingCloudCoreService, MarketingCloudLogin

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-10-20 15:15 UTC

   Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-20 10:40 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...

2. update 2026-10-20 10:57 UTC

   We restored email delivery by rolling back a recent change to an email service component. Customers now receive all new password reset and one-time passcode (OTP) emails. Some delayed emails remain queued, and we're flushing those queues so it delivers sooner. We'll perform a...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-21 22:43 UTC

   We’ve investigated and resolved an issue where Identity Resolution was not completing normally. Customers using the affected feature saw errors, and new data was not being populated in the unified profile table. Existing data remained usable. We traced the trigger to a recent...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-19 13:39 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...

2. update 2026-10-19 13:53 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...

3. update 2026-10-19 14:08 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...

4. update 2026-10-19 14:31 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...

5. update 2026-10-19 14:52 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...

6. update 2026-10-19 15:17 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...

7. update 2026-10-19 15:46 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...

8. impactRadiusIncrease 2026-10-19 16:12 UTC

   Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

9. update 2026-10-19 16:43 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,...

10. update 2026-10-19 17:10 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...

11. update 2026-10-19 17:36 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...

12. update 2026-10-19 18:05 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,...

13. update 2026-10-19 18:34 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...

14. update 2026-10-19 19:41 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....

15. impactRadiusIncrease 2026-10-19 20:25 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.

16. impactRadiusIncrease 2026-10-19 20:42 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. impactRadiusIncrease 2026-10-19 22:50 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. update 2026-10-19 23:43 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...

19. update 2026-10-20 01:04 UTC

    The queue backlog of pending jobs has been cleared, and, after a period of monitoring and validation, all services have been confirmed restored and operating as expected. Activation files and related data jobs are processing normally again. This incident has been declared...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: MarketingCloudCoreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: SALESFORCEORDERMANAGEMENT

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-10-19 02:18 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.

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: EventReceivingFeatures, PersonalizationFeatures

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Agentforce

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-10-14 18:53 UTC

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

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: LoadaView

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-16 06:15 UTC

   We've deployed the fix during off-peak hours to the affected US pods, and we've confirmed that workbooks are loading normally again. Originally posted here https://status.salesforce.com/incidents/20004486 We apologize for the impact this incident had on customers and their...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: LoadaView

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-15 06:38 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,...

2. update 2026-10-15 09:19 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...

3. impactRadiusIncrease 2026-10-15 16:42 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. update 2026-10-15 21:28 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...

5. update 2026-10-16 01:46 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...

6. update 2026-10-16 05:55 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.

7. update 2026-10-16 23:01 UTC

   Deployments have completed in all regions, and services are restored for all impacted customers. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: LoadaView

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-16 20:47 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,...

2. update 2026-10-17 04:29 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.

3. resolvedFeatureDegradation 2026-10-17 10:05 UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: LoadaView, PublishtoTableauCloud, WebEdit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolvedServiceDisruption 2026-10-13 18:40 UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the service disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: PublishtoTableauCloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-15 20:52 UTC

   We resolved an issue where some Prep flows that appended to a published data source showed fewer records than expected in the output data source. We applied a fix and restarted affected services. Affected customers can run a full refresh with the Create output option to refresh...

2. update 2026-10-15 22:14 UTC

   We have published the following Knowledge Article which provides specific instructions and recommendations for customers who may have been affected by this issue: https://help.salesforce.com/s/articleView?id=005461980&type=1

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: PublishtoTableauCloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-15 20:55 UTC

   We resolved an issue where some Prep flows that appended to a published data source showed fewer records than expected in the output data source. We applied a fix and restarted affected services. Affected customers can run a full refresh with the Create output option to refresh...

2. update 2026-10-15 22:07 UTC

   We have published the following Knowledge Article which provides specific instructions and recommendations for customers who may have been affected by this issue: https://help.salesforce.com/s/articleView?id=005461980&type=1

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-13 08:12 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'll provide an update in 30...

2. update 2026-10-13 08:40 UTC

   We completed the rollback of a recent deployment across all impacted instances. We restored access to shared data through external data warehouse integrations, and requests from connectors are succeeding. Customers can now resume using these integrations. Our investigation...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. impactRadiusIncrease 2026-10-09 23:27 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.

2. update 2026-10-09 23:40 UTC

   We’ve investigated and confirmed resolution of a third party performance degradation that impacted multiple Salesforce instances. Impacted customers may have experienced latency and errors. We apologize for how this incident affected you and your business. We will undertake a...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-08 14:31 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...

2. update 2026-10-08 14:48 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.

3. impactRadiusIncrease 2026-10-08 14:55 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. update 2026-10-08 15:24 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...

5. update 2026-10-08 15:56 UTC

   As of 15:21 UTC this performance degradation issue has been resolved. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to...

6. update 2026-10-08 19:32 UTC

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

7. impactRadiusIncrease 2026-10-08 19:32 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.

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-08 18:09 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...

2. update 2026-10-08 18:29 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...

3. impactRadiusIncrease 2026-10-08 18:42 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. startTimeRevision 2026-10-08 18:42 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...

5. update 2026-10-08 19:01 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...

6. update 2026-10-08 21:28 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...

7. update 2026-10-08 22:29 UTC

   We’ve resolved an issue affecting CRM Analytics recipe runs for a number of customers, preventing recipes from completing successfully. We rolled back the affected service to a prior stable version, and recipe runs have now returned to normal. We apologize for how this incident...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: APIManager, AnypointMonitoring, Exchange, RuntimeManager

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-07 06:45 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...

2. update 2026-10-07 11:16 UTC

   We’ve completed the remaining planned maintenance changes, including the final deployment covering five services. These features are now working as expected. We apologize for how this incident affected you and your business. We will undertake a full investigation of the...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. correctionFalsePositive 2026-10-06 19:07 UTC

   The Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any inconvenience caused by the false positive notification, and we...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Agentforce, Customer360Audiences

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-06 10:22 UTC

   We're investigating an issue affecting Data 360 where a subset of customers running SQL queries against their data in Data 360 may experience errors or delays. Customers are also unable to view Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. We have...

2. update 2026-10-06 10:41 UTC

   We’ve confirmed that restarting the affected components resolved the issue. Data 360 services are now working as expected including access to Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. Our investigation also confirmed that the impact was broader...

3. update 2026-10-06 10:55 UTC

   Upon further investigation, we’ve determined that the end time of the impact is different than initially understood. We’ve revised the end time of the Trust post to more accurately reflect when the issue was resolved for customers. We apologize for any confusion.

4. update 2026-10-06 15:27 UTC

   We’ve become aware that a subset of customers are continuing to experience errors when viewing certain records within Salesforce. We've identified the trigger as stale cached data remaining from the earlier issue and are running a process to clear the affected data and restore...

5. update 2026-10-06 15:58 UTC

   We’re continuing the process to clear the affected data and restore normal service. In the meantime, we've also published a Known Issue article containing workaround steps that affected customers can follow to view the impacted records. Known Issue Article:...

6. update 2026-10-07 02:41 UTC

   We’re continuing our efforts to clear the affected data to restore normal service. The data refresh is nearly complete and we are still clearing cached data that can cause errors. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup...

7. update 2026-10-07 08:38 UTC

   The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing the cached metadata. We’re running this process at a measured pace to protect the service for all customers. Some customers may still see intermittent errors when viewing Data...

8. update 2026-10-07 12:11 UTC

   The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing cached metadata. We’re running this process at a measured pace to protect service for all customers. Some customers may still see intermittent errors when viewing Data Lake...

9. impactRadiusIncrease 2026-10-07 17:13 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.

10. update 2026-10-07 21:56 UTC

    The cached metadata has now been cleared. After a period of monitoring, we have confirmed that access to Data Lake Objects is restored for all affected customers. We apologize for the impact on our customers and their businesses. A full investigation will determine the technical...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: LoadaView

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-06 16:56 UTC

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

2. update 2026-10-06 17:27 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....

3. update 2026-10-06 18:17 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...

4. update 2026-10-06 18:50 UTC

   Some Tableau Cloud users without Creator or Administrator roles were unable to view or access projects and workbooks assigned to them. We rolled back the recent platform update that introduced this issue, and project access is now fully restored. We apologize for how this...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-10-05 19:14 UTC

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

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences, analytics

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-04 13:31 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...

2. update 2026-10-04 14:01 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....

3. update 2026-10-04 14:30 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.

4. update 2026-10-04 15:22 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...

5. update 2026-10-04 16:45 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....

6. update 2026-10-04 18:09 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.

7. update 2026-10-04 20:06 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...

8. update 2026-10-04 22:23 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.

9. update 2026-10-04 22:36 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...

10. impactRadiusIncrease 2026-10-05 00:16 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.

11. update 2026-10-05 00:34 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...

12. update 2026-10-05 00:57 UTC

    We increased capacity on the affected internal services and restarted them, which restored normal operation at 00:25 UTC on October 5, 2026. CRM Analytics recipe runs and Data 360 segmentation tasks are running successfully, and we resolved the issue. Customers may need to run...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: AutomationStudio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: AutomationStudio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-10-02 23:29 UTC

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

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-10-02 18:45 UTC

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

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-01 22:19 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...

2. update 2026-10-02 16:54 UTC

   The issue affecting .mil network connectivity to some Salesforce GovCloud environments was resolved as of 14:50 UTC on October 2, 2026. Connectivity has remained stable during monitoring, and affected customers are no longer experiencing impact related to this incident. We...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: ServiceCloudMessagingChannels, ServiceCloudVoice

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-09-29 21:38 UTC

   We’re investigating an issue affecting Data Cloud streaming ingestion in a subset of environments. Customers may experience delays or failures when ingesting data through the Ingestion API, Web and Mobile Connector, or MCP Connector. We’ve identified service startup failures in...

2. update 2026-09-29 22:03 UTC

   We’re continuing to investigate the Data Cloud streaming ingestion issue and are moving forward with a rollback in one environment to validate recovery before expanding the action. In parallel, we’re investigating why the service is failing to start normally. We’ll provide...

3. update 2026-09-29 22:30 UTC

   We’ve started the rollback in an initial affected environment and are seeing early signs of recovery, though service capacity has not yet returned to expected levels. We’ve narrowed the investigation to a small number of production environments and are manually increasing...

4. update 2026-09-29 22:57 UTC

   We’ve successfully increased service capacity in one of the affected environments, and initial validation confirms the additional service instances are active. We’re applying the same targeted action to the remaining affected environments while addressing the issue that...

5. impactRadiusIncrease 2026-09-29 23:00 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. update 2026-09-29 23:44 UTC

   The issue affecting Data 360 streaming ingestion in a subset of environments has been resolved, after the service's capacity was increased. We apologize for how this incident affected you and your business. We'll undertake a full investigation of the incident, establishing the...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: B2CCore

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-09-29 06:31 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...

2. update 2026-09-29 07:00 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....

3. update 2026-09-29 07:35 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...

4. update 2026-09-29 08:00 UTC

   We’ve resolved the issue impacting Log Center by restarting the affected log collection component, restoring normal log flow. Through proactive monitoring, we identified and addressed additional affected PODs and implemented preventive actions across the fleet to mitigate...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: AccessManagement

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-28 09:24 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...

2. update 2026-09-28 09:57 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...

3. update 2026-09-28 10:18 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...

4. update 2026-09-28 10:33 UTC

   We've completed the rollback for all impacted regions, and logins are now successful. Customers are no longer experiencing single sign-on (SSO) login failures when logging in to Anypoint Platform via SSO. SSO logins were impacted only for customers whose org's stored Identity...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: MarketingCloudCoreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-02 21:25 UTC

   Between 20:55 UTC on September 25 and 18:46 UTC on September 26, customers using the Microsoft Teams connector may have been unable to authenticate or maintain their connection. Our team traced the issue to an expired authentication credential, immediately issued a new one, and...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Platform

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-25 18:53 UTC

   Recurrence of the earlier US2 incident — same root cause. The US2 Redis cache is again at its memory limit and rejecting writes. Impact:logins disruption

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: AnypointMonitoring, CloudHub20Spaces-AP-NORTHEAST-1, CloudHub20Spaces-AP-SOUTHEAST-1, CloudHub20Spaces-AP-SOUTHEAST-2, CloudHub20Spaces-CA-CENTRAL-1, CloudHub20Spaces-EU-CENTRAL-1, CloudHub20Spaces-EU-WEST-1, CloudHub20Spaces-EU-WEST-2, CloudHub20Spaces-SA-EAST-1, CloudHub20Spaces-US-EAST-1, CloudHub20Spaces-US-EAST-2, CloudHub20Spaces-US-WEST-1, CloudHub20Spaces-US-WEST-2

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-29 03:06 UTC

   On September 25, 2026, at 17:33 UTC, a subset of MuleSoft CloudHub 2.0 Private Space customers lost visibility into application logs, traces, and monitoring metrics. Application traffic kept processing without interruption. We rolled back the change in the EU and US regions, and...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: MarketingCloudLogin

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-25 09:12 UTC

   We're investigating an issue impacting login access to Stack 401 for Marketing Cloud Engagement. Affected users are unable to log in to this Stack. We've engaged multiple engineering teams to review database and caching services. We'll provide an update in 30 minutes or sooner...

2. update 2026-09-25 09:50 UTC

   As we continue to investigate the login issue impacting Stack 401 in Marketing Cloud Engagement, we identified timeout errors on login token requests and are reviewing the health of the caching and database services connected to this Stack. We’ve also identified a high volume of...

3. update 2026-09-25 10:26 UTC

   We've identified the specific integration that's generating a high volume of login requests to Stack 401 in Marketing Cloud Engagement and have applied rate limits to those requests. We’re validating the changes and monitoring login access. We've also confirmed there are no...

4. update 2026-09-25 10:40 UTC

   We’ve resolved the issue that prevented some Marketing Cloud Engagement users from logging in to Stack 401. We applied rate limits to the high volume of login requests, and all services are now operating normally. We apologize for the impact this incident had on you and your...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: B2CCore

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-25 11:35 UTC

   We're investigating an issue affecting Commerce Cloud users' ability to view site visit traffic data. Some customers are seeing zero values when accessing their traffic dashboard. Site visits are occurring, but the dashboard isn't displaying them. We've engaged our engineering...

2. update 2026-09-25 12:00 UTC

   We're continuing to investigate the issue and are working to fully understand the scope of the impact. We have confirmed that the traffic data is being recorded correctly it's just not displaying in dashboards. We'll provide an update in 30 minutes or sooner if additional...

3. update 2026-09-25 12:28 UTC

   We're working to understand why the data isn't being processed correctly. We're in the process of analyzing error logs to determine the trigger of the issue and possible remediation steps needed. We'll provide an update in 30 minutes or sooner if additional information becomes...

4. update 2026-09-25 12:50 UTC

   We’ve confirmed the trigger of the issue, the pipeline that processes the traffic data became blocked. We’re working to perform a configuration change to unblock the traffic data. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. update 2026-09-25 13:18 UTC

   We're continuing to perform the necessary configuration change to unblock the processing of the site visit traffic data. Once this is complete, we’ll validate that the processing of the backlog is has begun. We'll provide an update in 30 minutes or sooner if additional...

6. update 2026-09-25 13:44 UTC

   We’ve completed the necessary configuration change to unblock the site visit traffic data processing issue. The traffic data is expected to take several hours to completely process and appear in customer dashboards. We'll provide an update in 5 hours, or sooner if additional...

7. update 2026-09-25 13:49 UTC

   We've identified additional impacted instances and updated this messaging to reflect them. These customers will now receive communications about this incident going forward. These customers are also seeing zero values when accessing their site view traffic dashboard. We've...

8. update 2026-09-25 19:55 UTC

   We're continuing to monitor the remaining backlog as it processes, and expect it to fully populate over the next several hours. We'll provide another update as additional information becomes available.

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: B2BCommerce

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. impactRadiusIncrease 2026-09-25 02:50 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.

2. update 2026-09-25 02:58 UTC

   We identified a certificate expiry issue, disrupting requests to the Discovery service and causing search and index rebuild failures. We're validating certificate status across all impacted environments before rotating the certificate to restore service. We've also identified...

3. update 2026-09-25 03:21 UTC

   We've confirmed that certificate expiry triggered the issue and are now rotating certificates to restore service. This continues to affect search index rebuilds for a subset of B2B Commerce customers. We're generating new certificates for the affected regions. We'll first rotate...

4. update 2026-09-25 03:56 UTC

   We’ve generated the certificates required for rotation and are now working on the activation requests. The issue continues to affect search index rebuilds for a subset of B2B Commerce customers. We’ll provide an update in 30 minutes, or sooner if additional information becomes...

5. update 2026-09-25 04:22 UTC

   We've rotated the certificate in the first affected region and updated the search service. We're now validating the logs to confirm the fix before rolling out the certificate rotation across the remaining affected regions in parallel. We'll provide an update in 30 minutes or...

6. update 2026-09-25 05:21 UTC

   We're still validating the rotated certificate in the first affected region. We've also identified this issue affecting additional environments and are expanding our investigation to determine the full scope of impact. We'll provide an update in 30 minutes or sooner if...

7. impactRadiusIncrease 2026-09-25 05:31 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. update 2026-09-25 06:06 UTC

   We completed a certificate rotation and restarted application services in the first affected region, and validation confirmed this was successful. We're now rolling out the certificate rotation across the remaining affected regions in parallel. We'll provide an update in 30...

9. update 2026-09-25 06:28 UTC

   We resolved the search index errors affecting some B2B Commerce customers. We confirmed successful certificate rotation and service restoration across all affected regions, and customers can now rebuild search indexes normally. We apologize for how this incident affected you and...

10. startTimeRevision 2026-09-25 06:37 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...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: B2CCore

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Apps

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-09-24 15:09 UTC

   At 13:31 UTC on September 24, 2026, some Common Runtime customers began experiencing intermittent loss of application logs in the US region. Our engineers are working to resolve the issue.

2. update 2026-09-24 15:51 UTC

   Engineers are continuing to investigate this issue. The current known impact is intermittent router logs being dropped in a subset of US regions. App logs are unaffected. We will provide another update in the next 60 mins.

3. update 2026-09-24 16:10 UTC

   Engineers have fixed the issue and are monitoring. All router logs are now being successfully delivered.

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: EventReceivingFeatures, PersonalizationFeatures, UserInterface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-09-22 21:34 UTC

   We’ve resolved a service disruption affecting Marketing Cloud Personalization. Between 21:05 UTC and 21:10 UTC, customers may have been unable to access the user interface or use Event Receiving and Personalization features. Services have been restored and are operating...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: coreService

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigatingCauseOfIssue 2026-09-21 15:47 UTC

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

2. impactRadiusIncrease 2026-09-21 16:32 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. update 2026-09-21 16:44 UTC

   We're aware of an issue impacting performance where some customers may experience slower response times or delays when using core services on these instances. We have taken steps to increase system capacity on the impacted instances as we continue to investigate the underlying...

4. update 2026-09-21 17:15 UTC

   Some customers may still experience slower response times or delays when using core services on the impacted instances. We've identified the trigger of this issue as increased database session activity, which is driving elevated cache response times. We're remapping the impacted...

5. update 2026-09-21 17:43 UTC

   We've started remapping to the scaled cache cluster, and the change is still deploying. We expect full propagation across all impacted instances to take up to 60 minutes, after which traffic should stabilize. Some customers may continue to experience slower response times while...

6. update 2026-09-21 17:56 UTC

   All previously impacted instances recovered and performance returned to normal levels. We identified increased database session activity as the trigger and remapped the impacted instances to a newly scaled cache cluster to restore service. We apologize for how this incident may...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Customer360Audiences

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-19 23:46 UTC

   We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using...

2. update 2026-09-20 00:21 UTC

   We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an...

3. update 2026-09-20 01:45 UTC

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

4. resolvedFeatureDisruption 2026-09-20 05:46 UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: AdvertisingAudiences, AnalyticsBuilder, AudienceBuilder, AutomationStudio, CloudPages, ContactBuilder, ContentBuilder, EmailStudio, JourneyBuilder, MarketingCloudCoreService, MarketingCloudLogin, MarketingCloudRESTAPI, MarketingCloudSOAPAPI, MobileConnect, MobilePush, OtherFeature

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-09-18 13:24 UTC

   We're investigating an issue impacting a database supporting Marketing Cloud Engagement, and customers on the impacted database are currently unable to connect. Our investigation points to a potential file lock as the trigger. We've engaged additional support and are preparing a...

2. update 2026-09-18 13:49 UTC

   We're continuing to investigate a disruption impacting a database supporting Marketing Cloud Engagement, and affected customers remain unable to connect. We've identified that a storage-level lock is likely preventing the database from completing recovery, and our engineering...

3. update 2026-09-18 14:15 UTC

   We've ruled out a storage-level file lock as a factor in the ongoing recovery issue impacting Marketing Cloud Engagement. Affected customers remain unable to connect to services on the impacted database. We've started taking the database offline and bringing it back online in an...

4. update 2026-09-18 14:45 UTC

   We've performed an in-place restart of the impacted Marketing Cloud Engagement database which has moved into a recovery state. Affected customers remain unable to connect to services while recovery completes. We're monitoring progress closely. In parallel, we're preparing a...

5. update 2026-09-18 15:16 UTC

   Affected customers remain unable to connect to the Marketing Cloud Engagement database affected by this incident. We're now evaluating whether to continue recovery efforts on this database or move forward to our secondary database, which is fully prepared. We'll provide an...

6. update 2026-09-18 15:55 UTC

   We continue to work on restoring the Marketing Cloud Engagement database. A replacement of a failed component on the storage array has been planned, and is expected to take a few hours. The replacement will run parallel to our recovery work without affecting it. We'll provide an...

7. update 2026-09-18 16:22 UTC

   The Marketing Cloud Engagement database disruption is now resolved. We completed a failover to a secondary database, and services have returned to normal operation. Customers can now connect and use affected services as usual. We apologize for how this incident affected you and...

Excerpts are shortened. Read the full incident on Salesforce's status page.

Affected: Spiff

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigatingPotentialCause 2026-09-16 16:32 UTC

   We are investigating a potential cause of the issue.

2. update 2026-09-18 13:42 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 every two business days or...

3. update 2026-09-21 16:32 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 every 2 days or sooner if we have more information.

4. update 2026-09-23 20:13 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 every 2 days or sooner if we have more information

5. update 2026-09-25 15:45 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 every 2 days or sooner if we have more information.

6. update 2026-09-28 16:12 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 every 2 days or sooner if we have more information.

7. update 2026-10-01 18:48 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 every 2 days or sooner if we have more information

8. update 2026-10-05 21:18 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 every 2 days or sooner if we have more information

9. update 2026-10-07 19:51 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 every 2 days or sooner if we have more information

10. update 2026-10-09 15:14 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 every 2 days or sooner if we have more information

11. update 2026-10-12 20:15 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 every 2 days or sooner if we have more information.

12. update 2026-10-13 17:50 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 every 2 days or sooner if we have more information.

13. update 2026-10-14 16:15 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 every 2 days or sooner if we have more information.

14. update 2026-10-15 23:27 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 every 2 days or sooner if we have more information.

Excerpts are shortened. Read the full incident on Salesforce's status page.