We have identified additional instances experiencing this issue, Customers on these newly identified instances will receive communications about this incident. Multiple regions have already recovered

Update timeline

1. identified Jul 10, 2026, 03:52 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jul 10, 2026, 04:16 AM UTC

   We're aware of an issue at the network tier impacting multiple production instances. Services affected include Einstein Activity Capture and Conversation Intelligence. Customers using these services may experience failures, errors, or delays. The issue is under active investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 10, 2026, 04:48 AM UTC

   We've identified an infrastructure configuration change as the trigger. We're rolling back that change and will complete the necessary validation and verification following the rollback. Our investigation has revealed that the impact is broader than initially understood, and the affected services now include Marketing Cloud Engagement. Additional instances have been identified as impacted, and customers on these instances will receive communications about this incident. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 10, 2026, 05:25 AM UTC

   Our investigation has confirmed that a subset of customers may experience issues with MuleSoft and Marketing Cloud Engagement services. We're continuing to roll back the infrastructure change that triggered the issue. We've successfully restored and validated one production environment, and we're now executing rollbacks in parallel across the remaining affected production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 10, 2026, 05:50 AM UTC

   Customers may experience delays or errors when accessing the affected services while the rollback is in progress. We're rolling back the infrastructure change across all affected production instances, and we're validating the instances where the rollback is already complete. We expect the rollback to be complete in approximately 90 minutes. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.

6. monitoring Jul 10, 2026, 06:43 AM UTC

   We have identified additional instances experiencing this issue, Customers on these newly identified instances will receive communications about this incident. Multiple regions have already recovered following the rollback action, and remediation continues on those remaining. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.