Salesforce incident

Service disruption: DB402025, DB402026, DB402028 (+23 more)

Resolved after 37 minutes, affecting DB402025 and DB402026 and 1 more, on October 20, 2026.

monitoring Oct 20, 2026, 03:15 PM UTC

Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the databases to maintain stability We apologize for the impact this incident may have had on your customers and their businesses. We’ill complete a full investigation to confirm the technical trigger and underlying cause, and to identify actions that prevent a recurrence.

Started
Oct 20, 2026, 01:33 PM UTC
Resolved
Oct 20, 2026, 02:10 PM UTC
Duration
37m
Detected by Pingoru
Oct 20, 2026, 01:33 PM UTC

Affected components

DB402025DB402026DB402028DB402029DB402030DB402031DB402032DB402033DB402034DB402038

Update timeline

  1. identified Oct 20, 2026, 01:33 PM UTC

    Disruption Started: serviceDisruption

  2. resolved Oct 20, 2026, 02:10 PM UTC

    Resolved: Incident Resolved

  3. monitoring Oct 20, 2026, 03:15 PM UTC

    Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the databases to maintain stability We apologize for the impact this incident may have had on your customers and their businesses. We’ill complete a full investigation to confirm the technical trigger and underlying cause, and to identify actions that prevent a recurrence.

Your product runs on more than Salesforce

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →