Salesforce incident
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.
Salesforce experienced a major incident on April 27, 2026 affecting DB51002 and DB51003 and 1 more component, lasting 2h 39m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 27, 2026, 12:34 PM UTC
Disruption Started: marketingCloudDisruption
- monitoring Apr 27, 2026, 12:41 PM UTC
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.
- monitoring Apr 27, 2026, 01:18 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood and we've added DB51006 and DB51075 to this posting.
- monitoring Apr 27, 2026, 01:22 PM UTC
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.
- monitoring Apr 27, 2026, 01:42 PM UTC
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.
- monitoring Apr 27, 2026, 01:47 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood and we've added DB51038 and DB51219 to this posting.
- monitoring Apr 27, 2026, 02:10 PM UTC
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.