MuleSoft feature degradation

We have identified some new errors in the past 15 minutes, and we’re investigating the cause of the issue.

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

As informed earlier, we’re seeing steady improvements across the environment and are still monitoring performance metrics following the fix.

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

We’re seeing steady improvements across the environment and are actively monitoring performance metrics following the fix.

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

We've deployed an initial fix, and are monitoring health metrics. Our teams are noting positive signals, and some customers may observe signs of recovery when loading the application list display in Runtime Manager. We are adding capacity to our services in an attempt to alleviate impact.

Thank you for your patience as we work through this incident. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We're continuing to investigate the trigger of this issue and evaluating multiple remediation paths to restore services.

We'll provide an update in 120 minutes or sooner if additional information becomes available.

We continue to investigate the remaining issue affecting the application list display in Runtime Manager in the US region. Affected customers are unable to view their applications in the Runtime Manager UI; however, applications continue to run and are not impacted. We are actively working to restore full functionality.

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

We continue to monitor for full recovery in the US region. During this investigation, a separate issue affecting the application list display in Runtime Manager was identified and is being actively investigated.

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

We continue to monitor the US region for full recovery. In the interim, the workaround remains available where customers can use Anypoint Insights to search for their application and access it via the Manage Application link.

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

Anypoint Monitoring dashboards have recovered in the EU and are showing signs of recovery in the US. We continue to monitor for full recovery and provide an update in 60 minutes or sooner if additional information becomes available.

We've completed redeploying the affected services with a renewed certificate to the US, and impacted services there are now beginning to recover.

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

We've confirmed the expired certificate as the trigger. At 14:09 UTC, we began redeploying the affected services with a renewed certificate. Impacted EU services are now beginning to recover. We're deploying the fix to the US shortly.

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

Investigations have highlighted that a recently expired certificate may be the trigger and we're exploring this further.

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

In addition to previous guidance for monitoring, as a partial workaround for Runtime Manager, customers can use Anypoint Insights to search for their application and access it via the Manage Application link.

We're continuing to work towards resolution and will provide an update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue impacting Anypoint Monitoring and Runtime Manager. Customers can't view metric panels in the Anypoint Monitoring dashboard in the US and EU, and US customers can't see their applications in Runtime Manager. As a partial workaround for monitoring metrics, customers can use Anypoint Monitoring Insights.

We're investigating a connectivity issue as the likely cause and our teams are actively working toward resolution. We'll provide an update in 60 minutes or sooner if additional information becomes available.