Salesforce Data Cloud Activation Disruption Resolved After 13-Hour Outage
Highlight text, then choose “Suggest an edit”.Your selection is saved in the bottom bar.
Salesforce resolved a Data Cloud activation disruption on September 20, 2026, after the incident affected 14 listed instances for 13 hours and 41 minutes. The disruption began at 11:30 a.m. UTC on September 19 and ended at 1:11 a.m. UTC on September 20, according to the Salesforce Trust incident record. (status.salesforce.com)
Salesforce Data Cloud Activations Affected Across 14 Instances
The affected instances included AUS102, BRA14, BRA16, BRA18, BRA24, BRA28, BRA32, BRA34, BRA36, BRA48, BRA50, BRA58, CAN28, and CAN34. The incident affected Data Cloud activation processing rather than Salesforce access generally, so the practical impact was concentrated on customers using activation workflows in those environments.
Independent Salesforce service monitoring also recorded a feature service disruption on September 20, confirming that the event was not limited to an isolated customer report. (statusgator.com)
Third-Party Cloud Storage Identified as the Trigger
Salesforce identified a third-party cloud storage service used in its Prod1-CDP1 environment as the source of the activation errors. Engineers applied a configuration change to mitigate the issue and began preparing an alternate storage option as an additional safeguard.
Salesforce marked the incident resolved after observing stable service and said customers should no longer see an impact. Teams that rely on Data Cloud activations should still review failed or delayed activation jobs from the affected window before assuming downstream audiences, segments, or connected destinations were updated successfully.
