Is Salesforce down?

Degradation Started: performanceDegradation

Disruption Started: marketingCloudDisruption

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.

Degradation Started: muleSoftFeatureDegradation

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.

Disruption Started: serviceDisruption

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're investigating a widespread service disruption impacting Commerce Cloud and Core Services in the France region. Customers are currently experiencing a full disruption and are unable to log in to or access their services. Initial investigations show that the issue is due to a power failure in the data center. 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 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.

All Core services are recovered and available as of approximately 11:45 UTC. These instances will now be removed from this posting and will receive their own dedicated posting for this incident. Monitoring for recovery of Commerce Cloud services is still ongoing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to work to fully restore Commerce Cloud services following the power issue at our data center in France. The majority of PODs are fully back online and under monitoring, and we're restarting services on PODs 248, 258 and 356 as they're still experiencing some latent impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've determined that a site-switch for PODs 248, 258, and 356 is the most appropriate action to get customers out of impact and we're proceeding with this action now. All other PODs remain out of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We have determined that restarting services in place is the most effective path to resolution, and we are proceeding with this action now. A site-switch was not performed as we are resolving the issue through these in-place restarts. During this process, customers will see services begin to return in a staggered phase, often before the full restart is complete. The current status of the remaining instances is as follows: PODs 313 and 356: These instances have been confirmed as restored and are under monitoring. POD 248: The restart is currently in progress. Customers may begin to see service recovery on this instance shortly.All other PODs remain stable. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Disruption Started: marketingCloudDisruption

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.