Salesforce Outage History

We're aware of an issue impacting Agentforce. A subset of customers may encounter a "Something went wrong, please try again" error when accessing Agentforce across multiple instances. We're actively investigating potential triggers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to investigate this issue. We have deployed a fix on one of the impacted instances and are currently monitoring performance. If successfully validated, we will deploy the fix to all impacted instances to restore services as quickly as possible for customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health metrics across instances that have received the fix so far. We'll provide an update in 30 minutes or sooner if additional information becomes available.

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

We are aware that customers on AP60 are experiencing a high volume of errors when performing actions such as saving records, creating new records, and updating records. Users may be able to retry operations to temporarily work around errors. We are actively investigating the technical trigger and our teams are working on remediation steps, including an app server restart. We will provide an update in 30 minutes or sooner if additional information becomes available.

We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approach. Based on this success, we have initiated a rolling restart of all app servers on the AP60 instance. We will provide an update once the process is completed for all app servers or if additional information becomes available.

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

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

At 06:14 UTC on June 12, 2026, a feature degradation began impacting Object Store v2. As a result, customers are unable to store or retrieve keys that contain special characters. We have identified the technical trigger and a fix has been prepared. We are in the process of deploying it to all affected regions. There is no workaround available at this time. We will provide an update in 30 minutes or sooner if additional information becomes available.

Issue: We are aware of an issue affecting the Anypoint Management Center US that began on June 12 at 15:20 UTC. Impact: Customers in US production environments are experiencing an inability to list their applications in Runtime Manager within Anypoint Management Center US. Deployments to new API Omni Gateway (Flex) are also unavailable. Existing running applications are not impacted by this issue. We'll provide another update in 60 minutes or sooner if more information becomes available.

We are continuing to investigate the trigger for this incident and have determined that new Runtime deployments and customer alerts on Runtime Manager may be impacted as well. We'll provide another update in 60 minutes or sooner if more information becomes available.

We have identified the potential trigger for this incident and have taken action to mitigate impact. We are seeing improvements, but are continuing to monitor the environment to ensure the issue is resolved. We'll provide another update in 60 minutes or sooner if more information becomes available.

We have confirmed that all issues affecting the Anypoint Management Center US aside from API Manager alerts failing to trigger correctly have been resolved. We are continuing to investigate the API Manager Alerts and will provide another update in 60 minutes or sooner if more information becomes available.

The investigation into why API Manager alerts are not triggering as expected is ongoing, alongside active troubleshooting efforts. We will provide another update in 60 minutes or sooner if more information becomes available.

We're aware of an issue affecting agents using Messaging in our Core service. As a result, agents are unable to close active Messaging sessions from the UI. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've identified a source of excessive service usage and have taken steps to address this. We're monitoring and we'll provide an update in 30 minutes or sooner if additional information becomes available.

We noted an issue impacting Salesforce Field Services (SFS) Mobile on multiple instances. SFS Mobile customers who have the performance priming feature enabled may observe failures when using the syncing feature within the SFS Mobile application. We’ve identified the technical trigger as a recent deployment, and are performing rollbacks as our primary solution. We’ll provide an update in 30 minutes or sooner as additional information becomes available.

We're currently investigating an issue impacting the Shopper Agent feature, which allows users to interact with a chat-based assistant to search for and discover products on their Storefront, is currently not responding. Customers may be unable to receive responses from the Shopper Agent Guided Chat experience, impacting AI-powered shopping assistance, product recommendations, and related conversational commerce workflows. This is a feature that commerce customers deploy to their storefronts. We have identified a change introduced as part of a recent release as the cause of the issue and are actively working on a fix to restore normal functionality.

We’ve confirmed the issue is across multiple instances including production and linked to a permission configuration change introduced as part of a recent release. Due to related database considerations, a rollback is not a viable option. We’re currently working on an emergency release to restore the permission configuration, which is estimated to take several hours to build, validate, and deploy. We will provide an update in 60 minutes or sooner if additional information becomes available.

We continue our efforts to prepare the fix and deploy it via an Emergency Release. Testing and approval activities are in progress. Following that, the plan is to deploy the ERR to all the impacted instances where this release was deployed, which is expected to take several hours. We’ll provide an update as soon as significant new information becomes available.

The fix has been successfully validated in a test environment. We're working to secure the necessary approvals to include this fix in the next scheduled deployment at 15:00 UTC. We'll provide an update following the deployment of the fix to the impacted instances.

The fix will be implemented with the next daily deployment, which is scheduled to begin at 00:30 UTC on June 11, 2026. We'll provide an update following the deployment of the fix, or sooner if additional information becomes available.

We continue to prepare for the daily deployment. We will provide a new update once we have visibility of whether the fix has been deployed and validated, or sooner if new information becomes available. We apologize for any inconvenience this issue is causing to customers.

The Einstein Bots performance degradation is related to connection to WhatsApp. User messages sent via WhatsApp may be either delayed, dropped, or not processed by the Agentforce bot, which is causing customers to be stalled mid-conversation with no error. Engineering has identified the trigger and is taking corrective action to increase capacity to mitigate this issue. Initial monitoring is showing positive results. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

User messages sent via WhatsApp may continue to see some delay or unexpected results. While the increases in capacity that were implemented had initially shown positive results, our monitoring still shows some increased errors. We are moving forward with further additions to capacity for chatbot services. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue impacting Commerce Cloud customers on some pods. As a result, customers are experiencing intermittent Storefront unavailability, with sites going down for periods ranging from 30 minutes to an hour. We've deactivated a replication feature on impacted pods as an interim measure to reduce further Storefront impact. We're also working to revert the runtime environment on impacted pods back to a previous version, and have begun updating pod configuration files and restarting application servers to validate this change. We'll provide an update in 30 minutes or sooner if additional information becomes available.

The cause has been identified as a behavior change introduced by a recent runtime upgrade. To reduce further impact, we've disabled a replication feature for affected customers., We're now preparing a fix to revert the runtime environment to its previous version, which will take approximately 90 minutes to deploy and will be followed by a non-disruptive rolling restart across the impacted PODs. We'll provide an update in 30 minutes, or sooner if new information becomes available.

We’re reverting the runtime environment to its previous version across all impacted PODs via a fix that is estimated to take 45 minutes followed by a non-disruptive rolling restart. As a temporary measure, we have proactively disabled the Granular Data Replication feature to reduce further Storefront impact for affected customers We'll provide our next update in 30 minutes, or sooner if new information becomes available.

Storefronts were confirmed out of impact at 13:41 UTC. Granular Data Replication remains temporarily unavailable. Non-disruptive rolling restarts are now in progress on affected PODs to complete the revert of the runtime environment to the previous version. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Storefronts are no longer in impact. Non-disruptive rolling restarts continue to complete the revert of the runtime environment to the previous version. Granular Data Replication remains temporarily unavailable, this will be re-enabled after validation of restart completion. We will provide an update once the restarts are complete, or sooner if additional information becomes available.

We are investigating a recurrence of performance degradation across multiple instances. Impacted users are experiencing elevated Average Page Times (APTs) when using managed packages on Salesforce services. Our teams are actively reviewing the cause of the recurrence and working to mitigate the impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We're continuing to investigate the recurrence of slow page load times customers are experiencing. We have identified increased traffic levels as a contributing factor and have implemented mitigation measures across the impacted instances to help stabilize performance. We're actively monitoring the environment and evaluating the effectiveness of these actions as our investigation continues. We'll provide an update in 60 minutes or sooner if additional information becomes available.

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

We are investigating a performance degradation on multiple instances, where users are experiencing high Average Page Times (APTs) when using managed packages on Salesforce services. We believe this may be due to a recent change and are investigating to identify the root cause and take remediation actions. We will provide an update in 30 minutes, or as soon as new information becomes available.

We believe that we've identified the root cause of the slow page load times customers are experiencing when using managed packages on Core services. Multiple orgs running package installations simultaneously are causing the database to become overloaded, resulting in response times above normal thresholds. We've applied a throttle to the affected instances to limit the number of concurrent package installations and reduce the load on the database. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate the slow page load times customers are experiencing. We’ve identified that the issue is being driven by a high volume of automated requests targeting a specific page used for package installations. We've applied rate limits across the affected instances, and additional traffic mitigation actions are underway. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We believe that we've identified the root cause of the slow page load times customers are experiencing when using managed packages on Core services. Multiple orgs running package installations simultaneously are causing the database to become overloaded, resulting in response times well above normal thresholds. We've applied a throttle to the affected instances to limit the number of concurrent package installations and reduce the load on the database. We'll provide an update in 30 minutes or sooner if additional information becomes available.

At 22:31 UTC, June 06, 2026, a feature degradation began impacting Marketing Cloud customers on two Hyperforce stacks. As a result, links embedded in marketing emails are not redirecting recipients to the intended destination - recipients are landing on an error page instead. We are actively working to address this issue. We will provide an update in 30 minutes or sooner if additional information becomes available.

We continue to address a feature degradation affecting Marketing Cloud customers on two Hyperforce stacks. Links embedded in emails are redirecting to an error page, and open and click tracking data is not being recorded. Our teams have applied a configuration change intended to allow new email sends to function correctly going forward. We are currently validating that this change is working as expected. We are also continuing to investigate the technical trigger to determine the best path to resolution. We will provide an update in 30 minutes or sooner if additional information becomes available.

We’re investigating a performance degradation impacting multiple instances. During this time, a subset of customers using Search Analytics may experience a delay in their search interaction results between May 18, 2026, and May 28, 2026. While new data on the Data Lake Object (DLO) is flowing correctly following the resolution of a previous incident, the historical data from that window is currently being restored. We’ve successfully validated a fix in one of our production environments and are deploying it across the remaining impacted instances. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We’re actively deploying the fix across all remaining instances while closely monitoring system performance to ensure stability. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We continue to deploy the fix across all remaining instances while closely monitoring system performance to ensure stability. We’ll provide an update once additional information becomes available.

A feature degradation is causing complete failures for customers attempting to use activations to Meta Custom Audiences (also referred to as Facebook activations).

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

We continue to investigate an issue affecting customers using the Snowflake Data Share feature within Data 360. The fix has been successfully deployed to our ‌testing environment and is being monitored. Full deployment across all production environments remains in-progress; however, progress is currently delayed due to a secondary infrastructure issue impacting our deployment pipeline. Engineering teams are actively working to resolve this blocker. We'll provide an update within 60 minutes or sooner if additional information becomes available.