Salesforce incident
A recent deployment introduced a misconfiguration in our US and EU environments, which has been identified as the likely cause of the issue. We're currently deploying a fix and monitoring the situatio
Salesforce experienced a minor incident on May 29, 2026 affecting ANYPOINTMANAGEMENTCENTER-EU and ANYPOINTMANAGEMENTCENTER-US and 1 more component, lasting 4h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 29, 2026, 04:52 AM UTC
Degradation Started: muleSoftFeatureDisruption
- monitoring May 29, 2026, 05:29 AM UTC
The MuleSoft CloudHub 2 and Runtime Fabric services are currently experiencing an issue that prevents customers from deploying new applications. Existing running applications are not affected. We're actively investigating the cause and exploring paths to resolution. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 29, 2026, 06:18 AM UTC
We continue to investigate the issue where customers are unable to deploy new applications on CloudHub 2 and Runtime Fabric. Existing running applications remain unaffected. We have identified a recent release as the cause of this issue and are preparing to roll back the release. We'll provide an update within 60 minutes or sooner if the situation changes.
- monitoring May 29, 2026, 07:03 AM UTC
We continue to investigate an issue impacting MuleSoft Anypoint Platform where customers are unable to deploy new applications on CloudHub 2 and Runtime Fabric. Existing running applications remain unaffected. While preparing for the rollback the team identified customers running self-managed Flex Gateways in connected mode may experience Domain Name System (DNS) resolution failures preventing connectivity to the Anypoint Platform control plane. Existing running applications and APIs are not impacted. Our engineering team has identified a configuration change as the likely root cause and is actively working to resolve this issue. We will provide an update within 60 minutes or as soon as additional information is available.
- monitoring May 29, 2026, 08:15 AM UTC
A recent deployment introduced a misconfiguration in our US and EU environments, which has been identified as the likely cause of the issue. We're currently deploying a fix and monitoring the situation. We'll provide another update within 60 minutes, or sooner if additional information becomes available.