Salesforce Outage History

We're aware of a performance degradation impacting Anypoint MQ services. A subset of customers may experience errors when their applications attempt to interact with the message queue. We're actively working to restore full service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We have restored service for the related telemetry and ingestion functionality; however, some customers may still see connection loss errors when their applications interact with the message queue. We're investigating the remaining connectivity issues, and working with our third-party infrastructure providers to isolate the cause and restore full service. We'll provide another update in 60 minutes or sooner if additional information becomes available.

On further analysis, we've narrowed the issue down to a network routing and connectivity problem within the underlying infrastructure. We have teams focused on this component and continue to work closely with our third-party infrastructure providers to isolate the trigger and restore full service. We'll provide another update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue impacting agent metadata services resulting in a subset of customers experiencing issues retrieving or deploying agent metadata. The team has identified and validated a fix, and are preparing for deployment to the impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We are aware of an issue affecting Einstein Voice for Agentforce (AFV). As a result, customers are unable to create new voice sessions. We've identified a configuration issue and are working to deploy a fix on an expedited basis. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to investigate an issue affecting Agentforce Voice where a subset of customers may be unable to initiate new voice sessions. We've identified an issue with ‌metadata configuration and are working to deploy a fix which is expected to take several hours. We'll provide an update in 120 minutes or sooner if additional information becomes available.

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.

As we have confirmed this issue to only be impacting sandbox environments, all production instances have been removed from this post. We are continuing to work on the fix for this issue and will provide an update when additional information becomes available.

We’ve successfully validated the fix and are preparing to deploy it to all impacted environments. We’ll provide the next update as additional information becomes available.

At 03:13 UTC, May 5, 2026, we noted an issue impacting online Tableau Cloud services where multiple POD’s may be impacted due to Multi-Factor Authentication issues (MFA). Customers trying to log into their Tableau Cloud sites using MFA may have trouble with login issues. We're ‌actively engaged and are exploring multiple paths to resolution. We’ll keep you posted in 30 minutes or sooner, once additional information is available.

Our initial investigation indicates that authentication requests to a backend verification service are failing with authorization errors preventing successful login attempts. We've initiated a rolling restart on one of the impacted PODs and initial testing looks positive. We're now proceeding ‌with a rolling restart of services for the other impacted POD’s. We remain focused on stabilizing these services and are actively monitoring the environments. We’ll share the next update in 30 minutes or sooner, once additional information is available.

The rolling restart is currently underway for the remaining POD’s. We’re actively monitoring each environment post-restart to confirm full recovery. We’ll share the next update in 60 minutes or sooner as additional information is available.

On May 1, 2026 at 15:15 UTC we detected a feature disruption impacting the Data Cloud CRM Connector. Customers may experience data stream jobs failing or getting stuck. We are investigating the issue to identify the cause and remediate the issue. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

We are continuing to work on identifying the cause of the issue, including partnering with our third-party provider to analyze logs to identify the cause of the errors. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

We have determined that the issue is occurring due to insufficient infrastructure capacity. In collaboration with our third-party provider, we have rolled back a recent change, and are now monitoring how jobs are performing. We’ll provide another update in the next 60 minutes or sooner, if additional information becomes available.

This issue is impacting a subset of customers, and the service should be available for other users.

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

We continue to investigate an issue impacting customers using Commerce Cloud and Core services in our France-based infrastructure. Network connectivity began restoring at 11:22 UTC following a power event at our data center. While network links have come back online, services remain in recovery. 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 and we've added DB51006 and DB51075 to this posting.

Monitoring for recovery of Marketing Cloud services is still ongoing and customers should be seeing signs of recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

As of 12:46 UTC, all Marketing Cloud services are recovered. Out of an abundance of caution, we'll continue to monitor services for a further short period. 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 and we've added DB51038 and DB51219 to this posting.

Investigations have highlighted that the impact radius is broader than initially understood and we've added DBs 51090, 51237, 51156, 51062, and 51081 to this posting.

Customers using Runtime Manager may be unable to load the Applications list in the Runtime Manager UI, or receive errors when calling the Applications Application Programming Interface (API) directly (/armui/api/v2/applications). Users can't view or manage deployed applications. Refreshing the page may reload the Applications list successfully; the UI auto-refresh may also surface data. Other Runtime Manager functions aren't affected. We're actively working on resolving the issue. We'll provide an update when additional information becomes available.

Following a thorough investigation, we have determined that the scope of impact is narrower than initially thought. This post has been updated to reflect only the regions impacted. We apologize if this caused any inconvenience.

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’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.

The Salesforce Technology team is investigating a performance degradation that impacts Government Cloud Plus instances. This issue affects users utilizing .mil domain naming system (DNS) domains. The Technology team is working with a third-party vendor to troubleshoot the issue. As a result of this issue, affected customers may encounter difficulties accessing their sites or may experience reduced performance. Customers who are utilizing .mil domain naming system (DNS) domains are advised to create a customer case with your .mil DNS vendor to help expedite the resolution. Further updates will be provided as more information becomes available.