Salesforce experienced a Change Data Capture (CDC) feature degradation starting March 10, 2026, when a system update generated an excessive number of events, creating backlogs across multiple instances and causing event notifications to be delayed, missing, or out of order. The incident affected multiple global instances including USA660S, with most instances recovering after teams paused the message queue job causing the event surge. The final affected instance (USA660S) was resolved after 257.5 hours of degraded service.
The Change Data Capture (CDC) events backlog has cleared on GBR88 as of 17:47 UTC on March 22, 2026. CDC processing has returned to normal levels for customers on this instance. We will now remove the GBR88 instance from this Trust posting and they will receive a separate post to accurately reflect the correct impact times.
We are continuing to work on clearing the backlog for the remaining impacted instance (USA660S) and the next update will be upon a significant change in status, or sooner if additional information becomes available.
The Change Data Capture (CDC) events backlog has cleared on USA9018S as of 12:10 UTC on March 20, 2026. CDC processing has returned to normal levels for customers on this instance. We will now remove the USA9018S instance from this Trust posting and they will receive a separate post to accurately reflect the correct impact times.
We are continuing to work on clearing the backlog for the remaining two impacted instances (GBR88 and USA660S) and the next update will be upon a significant change in status, or sooner if additional information becomes available.
We are continuing our efforts to clear the existing backlog for GBR88, USA660S, and USA9018S instances and are actively monitoring the progress.
We'll provide an update upon a significant change in status, or sooner if additional information becomes available.
We have taken action to pause the source of the event surge, which has allowed the majority of impacted instances to recover.
The following instances have returned to normal operation:
USA880S (recovered March 14, 2026, at 04:30 UTC)
SWE64 (recovered March 11, 2026, at 23:10 UTC)
USA330 (recovered March 12, 2026, at 17:55 UTC)
USA892S (recovered March 12, 2026, at 22:00 UTC)
USA870S (recovered March 11, 2026, at 01:15 UTC)
IND110 (recovered March 16, 2026, at 20:30 UTC)
DEU60 (recovered March 11, 2026, at 00:20 UTC)
The following instances remain impacted and our teams continue to work toward full resolution:
GBR88
USA660S
USA9018S
For USA660S, we are implementing a targeted remediation to clear the event backlog. We are also working on the service responsible for the event surge to prevent recurrence.
We'll provide an update upon a significant change in status, or sooner if additional information becomes available.
We've paused the related message queue job to stop new events and allow the backlog to clear. Most instances have recovered, and the remaining ones are still processing their backlogs.
We'll provide an update upon a significant change in status, or sooner if additional information becomes available.
Starting at 07:24 UTC on March 10, 2026, Change Data Capture events began experiencing delays across multiple instances due to an update generating a large number of events. As a result, some customers may notice that certain event notifications are delayed, missing, or appear out of order.
We're currently working to resolve the issue and clear the backlog. The next update will be provided once the backlog is fully cleared, which is currently estimated for Monday, March 16, 2026.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with