Salesforce incident
We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list.
Salesforce experienced a minor incident on September 19, 2026 affecting AUS102 and BRA14 and 1 more component, lasting 6h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 19, 2026, 11:13 PM UTC
Degradation Started: featureServiceDisruption
- monitoring Sep 19, 2026, 11:46 PM UTC
We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.
- monitoring Sep 20, 2026, 12:21 AM UTC
We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.
- monitoring Sep 20, 2026, 01:45 AM UTC
We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. Meanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.