We continue to restore affected MuleSoft Private Spaces using the validated recovery method, with environments returning to a healthy state as remediation progresses. In parallel, we're also working w

Update timeline

1. identified Aug 19, 2026, 01:50 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Aug 19, 2026, 02:07 PM UTC

   We're aware of an issue affecting MuleSoft sandbox environments in a subset of private spaces across the EU and US. Approximately 42 private spaces are currently degraded, blocking customer sandbox patching and pipeline deployments. Running applications and production environments aren't impacted. We've paused further patching to prevent additional impact and are actively investigating a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Aug 19, 2026, 02:44 PM UTC

   We continue to investigate the MuleSoft sandbox patching issue affecting a subset of private spaces. One impacted space was recovered via a node restart, and we're validating this fix across all other impacted spaces. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

4. monitoring Aug 19, 2026, 02:59 PM UTC

   We continue to investigate the sandbox patching issue affecting Private Spaces. The impact radius has now increased to approximately 70 spaces across the EU and US. Node restarts proved ineffective and have been discontinued. We now believe a network configuration change in a recent platform release is the likely trigger. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

5. monitoring Aug 19, 2026, 03:50 PM UTC

   We continue to investigate the issue affecting sandbox patching and pipeline deployments in a subset of MuleSoft Private Spaces. Our teams are working with our third-party infrastructure provider to further investigate the network connectivity issues and determine the path to recovery. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

6. monitoring Aug 19, 2026, 04:58 PM UTC

   We identified the technical trigger as a third-party service limitation. We're working with our third-party infrastructure provider to implement changes needed to restore the affected environments and resume pending upgrades. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

7. monitoring Aug 19, 2026, 06:15 PM UTC

   We successfully validated a recovery method and are applying it to the remaining affected environments. In parallel, we're continuing to work with our third-party infrastructure provider to address the underlying service limitation and prevent additional impact. Running applications remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

8. monitoring Aug 19, 2026, 07:22 PM UTC

   We continue to apply the validated recovery method to affected MuleSoft Private Spaces, with environments returning to a healthy state as remediation progresses. We're also working with our third-party infrastructure provider to address the network-related issue and prevent additional impact. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available.

9. monitoring Aug 19, 2026, 08:54 PM UTC

   We continue to restore affected MuleSoft Private Spaces using the validated recovery method, with environments returning to a healthy state as remediation progresses. In parallel, we're also working with our third-party infrastructure provider on additional changes to prevent recurrence. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available.