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.

Major Resolved View vendor source →
Started
Apr 27, 2026, 12:34 PM UTC
Resolved
Apr 27, 2026, 03:13 PM UTC
Duration
2h 39m
Detected by Pingoru
Apr 27, 2026, 12:34 PM UTC

Affected components

DB51002DB51003DB51006DB51009DB51012DB51038DB51046DB51048DB51052DB51053DB51057DB51062DB51067DB51069DB51075DB51081DB51090DB51095DB51096DB51108DB51128DB51134DB51135DB51156DB51199DB51202DB51203DB51204DB51211DB51212DB51213DB51214DB51219DB51237DB51502

Update timeline

  1. identified Apr 27, 2026, 12:34 PM UTC

    Disruption Started: marketingCloudDisruption

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

Looking to track Salesforce downtime and outages?

Pingoru polls Salesforce's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Salesforce reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Salesforce alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Salesforce for free

5 free monitors · No credit card required