Salesforce incident
We have successfully completed validation of the fix in our test environment and have begun rolling it out to production. Our teams will continue deploying the fix across all remaining impacted enviro
Salesforce experienced a minor incident on August 20, 2026 affecting ARE2S and ARE4S and 1 more component, lasting 3d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 20, 2026, 09:01 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Aug 20, 2026, 09:09 PM UTC
We're investigating an issue affecting Private Connect where some customers may experience degraded connectivity to Salesforce services. We've identified a recent change as the likely trigger and are working to deploy a fix. Additional teams have been engaged to help progress the remediation. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Aug 20, 2026, 10:12 PM UTC
We are continuing to develop and validate a fix for this issue before deploying it to the affected environments. We will provide another update as significant progress is made or sooner if additional information becomes available.
- monitoring Aug 21, 2026, 01:59 AM UTC
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring Aug 21, 2026, 02:17 AM UTC
We’ve developed a fix for this issue and deployed it to test instances for validation before a wider rollout. Once validation is complete, we will deploy the fix to all impacted environments. We'll provide another update as significant progress is made or sooner if additional information becomes available.
- monitoring Aug 21, 2026, 04:29 AM UTC
We have successfully completed validation of the fix in our test environment and have begun rolling it out to production. Our teams will continue deploying the fix across all remaining impacted environments while closely monitoring services. We will provide another update as significant progress is made or sooner if additional information becomes available.