Salesforce incident

We completed the deployment of a fix to all six impacted stacks and we’ve now entered a monitoring phase to ensure the settings have fully propagated. We will begin the validation of the fix at approx

Salesforce is currently experiencing a minor incident affecting DB1 and DB10 and 1 more component, which began 49 min ago. The vendor's full update timeline is below.

Started
May 20, 2026, 08:01 PM UTC
Resolved
Ongoing
Duration
● 49m
Detected by Pingoru
May 20, 2026, 08:01 PM UTC

Affected components

DB1DB10DB100DB10000DB10001DB10002DB10003DB10004DB10005DB10006

Update timeline

  1. identified May 20, 2026, 08:01 PM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring May 20, 2026, 08:04 PM UTC

    At approximately 16:00 UTC on May 20, 2026, we became aware of a feature degradation impacting a subset of Marketing Cloud Engagement customers. A recent deployment that manages unsubscribe link processing has introduced an issue where some unsubscribe requests may not be successfully processed. This issue specifically impacts customers on Stacks 1, 5, 6, 7, 10, and 51 who utilize custom CloudPages for their unsubscribe branding or behavior. We estimate that roughly 25% of unsubscribe links may not properly process during an unsubscribe attempt. We have identified the trigger and are currently preparing remediation steps to restore normal functionality. We will provide an update in 30 minutes, or sooner if additional information becomes available.

  3. monitoring May 20, 2026, 08:26 PM UTC

    We completed the deployment of a fix to all six impacted stacks and we’ve now entered a monitoring phase to ensure the settings have fully propagated. We will begin the validation of the fix at approximately 20:30 UTC. We will provide an update in 60 minutes, or sooner if additional information becomes available.