We've restored all other previously impacted private spaces to normal operation. We continue to work on restoring the impact to private CloudHub 2.0 space in the US-EAST-1 region where customers may b

Update timeline

1. identified Sep 01, 2026, 09:45 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring Sep 01, 2026, 09:45 PM UTC

   We’ve identified some private spaces on which customers might not be able to deploy new applications, update existing applications, scale applications up or down, or restart applications. MuleSoft engineering is working on a mitigation, during which, impacted customers will observe their applications being graceful terminated and restarted. No action is needed from customers during this operation We'll provide another update as additional information becomes available.

3. monitoring Sep 02, 2026, 04:47 AM UTC

   We have made significant progress restoring most of the private spaces affected by this issue, with the majority now in a healthy state. We're continuing network configuration and certificate management fixes for the remaining spaces so customers can resume deploying, updating, restarting, and scaling applications. We'll provide an update as additional information becomes available.

4. monitoring Sep 02, 2026, 05:14 PM UTC

   We've restored all other previously impacted private spaces to normal operation. We continue to work on restoring the impact to private CloudHub 2.0 space in the US-EAST-1 region where customers may be unable to deploy, update, restart, or scale their applications. We'll provide an update as additional information becomes available.