Salesforce incident

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.

Major Resolved View vendor source →

Salesforce experienced a major incident on April 25, 2026 affecting DB6012, lasting 2h 43m. The incident has been resolved; the full update timeline is below.

Started
Apr 25, 2026, 10:41 PM UTC
Resolved
Apr 26, 2026, 01:24 AM UTC
Duration
2h 43m
Detected by Pingoru
Apr 25, 2026, 10:41 PM UTC

Affected components

DB6012

Update timeline

  1. identified Apr 25, 2026, 10:41 PM UTC

    Disruption Started: marketingCloudDisruption

  2. monitoring Apr 25, 2026, 11:41 PM UTC

    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.

  3. monitoring Apr 26, 2026, 12:09 AM UTC

    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.