MuleSoft feature degradation

We have applied a mitigation to the impacted instances, and initial monitoring is showing positive results. Our teams are currently performing additional monitoring and health checks across these instances. Some customers may now see success managing and viewing deployed apps.

After further analysis, it was determined that this issue only impacts Runtime Plane-US, CloudHub 2.0 Applications - US-EAST-1, CloudHub 2.0 Applications - US-EAST-2, Anypoint Management Center - US, and Runtime Manager. This post has been updated to reflect the most accurate understanding of impacted instances and services.

We’ll provide an update when as more information becomes available.

The workaround has been validated. We are also working to address a side effect identified while troubleshooting.

We’ll provide an update when additional information becomes available.

We are actively exploring multiple paths to remediation. We’ll provide an update when additional information becomes available.

Initial investigations show that the impact is specific to Spaces patched to the July 25 version and the us-east-1 and eu-west-1 regions. The July version of the deployment to production instances has been put on hold, and the June version is set as the default for any new spaces, as the rollback cannot be performed. We have updated this post to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

We are currently working to validate a workaround to assist customers. In parallel, we are working on a fix that will be tested before being deployed this weekend.

We’ll provide an update when additional information becomes available.

We are investigating issues affecting private and shared spaces where customers can’t view the status of deployed apps or manage them properly. This issue does not impact applications that are currently running and impacts spaces updated to the July 25 version. The June version will be set as the default for any new spaces. We are rolling back one of the impacted spaces to the June version to check if that fixes the issue and are halting further release of the change.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.