Loading

MuleSoft - Runtime Manager UI and Design Center UI impacted in EU & US Region - Wednesday, September 24, 2025

Date de publication: Oct 7, 2025
Description

Issue Summary

We sincerely apologize for the impact this issue caused you and your business. We understand that you rely on MuleSoft to run your business, and we are committed to learning from these issues and improving our platform to avoid similar issues in the future.

This section describes the impact our customers may have experienced.

On Tuesday, September 23, 2025 between 4:41 PM PT and Wednesday, September 24, 2025 at 04:14 AM PT ( Tuesday, September 23, 2025 between 11:41 PM UTC and Wednesday, September 24, 2025 at 11:14 AM UTC), customers were unable to view the Runtime Manager UI. They were able to use MMP (Mule Maven Plugin)/CLI/API as a temporary workaround. Customers using Design Center were unable to create, delete or rename API projects.

Impacted ProductsImpact Duration
Runtime Manager693 minutes
Design Center693 minutes

 

Issue Description

This section describes how the issue evolved.

On Wednesday, September 24, 2025, at 1:36 AM PT (8:36 AM UTC), an investigation began into reports of customers experiencing issues in the Runtime Manager UI. It was reported that customers were unable to view or manage their applications in Runtime Manager UI. They were able to use MMP (Mule Maven Plugin)/CLI/API as the temporary workaround. Customers using Design Center were unable to create, delete or rename API projects. The investigation identified that a change to the infrastructure impacted the Runtime Manager and Design Center UIs. The change was rolled back to the impacted services, ending the impact at 04:14 AM PT ( 11:14 AM UTC).

 

Root Cause

As a part of the MuleSoft uplift to the Hyperforce infrastructure, a new hostname was introduced through a slow rolling change for the CDN ( Content Delivery Network) that delivers static assets. The impacted customers had specific allowlists in their firewall, which prevented them from accessing this new hostname (example cdn.us1.mulesoft-cp.aws-prod1-useast1.aws.sfdc.cl for US).

 

Résolution

MuleSoft Remediation Actions

To address the identified root cause, MuleSoft commits to the following actions to help remediate the potential for these issues to occur in the future:

  • Remove the need to allowlist a new CDN Hostname during infrastructure uplift. We expect this to be available by October 31, 2025.
  • Improve testing to emulate enterprise customer setups including allowlisting in firewalls. We expect this to be available by October 31, 2025.

 

Our commitment to you:

We sincerely apologize for the impact this issue caused you and your business. It is our goal to provide world-class service to our customers, and we are continuously assessing and improving our tools, processes, and architecture to provide our customers with the best service possible.

If you have additional questions or need further support, please open a case with Support via the Help portal.

Numéro d’article de la base de connaissances

005225098

 
Chargement
Salesforce Help | Article