Monitoring - RTF customers running Mule workloads on self-managed Azure (AKS) platforms are advised to not upgrade their kubernetes infrastructure to version k8s1.25 due to a known cgroupsv2 interoperability issue with JDK8 used in the Runtimes. We will notify when a Mule Runtime update with the appropriate patch for this interoperability issue is available.
May 23, 2023 - 16:53 PDT
Anypoint Management Center Operational
Access Management Operational
API Manager Operational
Runtime Manager Operational
API Analytics Operational
Anypoint Monitoring Operational
API Functional Monitoring Operational
Anypoint Security Operational
Secrets Manager Operational
Security - Edge Operational
Tokenization Operational
Communities and Engagements Operational
API Community Manager Operational
Exchange Operational
Design Center Operational
Flow Designer Operational
API Designer Operational
API Mocking Service Operational
Design Center Projects Operational
Runtime Services Degraded Performance
Runtime Fabric Degraded Performance
Anypoint MQ Operational
Object Store v2 Operational
Scheduler Operational
Log Aggregator Operational
Insights Operational
Persistent Queues Operational
Object Store v1 Operational
Anypoint Partner Manager v2 ? Operational
Anypoint Visualizer Operational
Data Gateway Operational
DataGraph Operational
Dataloader Operational
Documentation Operational
MuleSoft Composer for Salesforce Operational
MuleSoft Composer Operational
MuleSoft Help Center Operational
MuleSoft RPA ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 31, 2023

No incidents reported today.

May 30, 2023

No incidents reported.

May 29, 2023

No incidents reported.

May 28, 2023

No incidents reported.

May 27, 2023

No incidents reported.

May 26, 2023
Resolved - As of 12:00 PM PT we are declared this issue as resolved, we reiterate our commitment to our customers and will be providing an RCA via our Help center in the next days.

Once more, we appreciate your patience.

May 26, 12:05 PDT
Monitoring - We finished processing all data and all CloudHub 2.0 applications in the us-east-2(Ohio) region should be fully operational, if you are experiencing problems feel free to reach out to support.

Once more we appreciate your patience during this issue.

May 26, 11:23 PDT
Update - A high percentage of applications are back online for CloudHub 2.0 customers in the us-east-2(Ohio) region, our internal systems are processing all the data to complete this task, we appreciate your patience while we work to fully restore the applications.
May 26, 10:30 PDT
Update - The process to bring back applications is still working, CloudHub 2.0 customers with applications in the us-east-2 (Ohio) region will see more applications coming back online, we are actively working towards fully resolution.

Thanks for your patience.

May 26, 09:46 PDT
Update - More applications are coming back online, CloudHub 2.0 customers with applications in the shared space us-east-2 (Ohio) will see recoveries, we are still working on making sure all applications are back online.

Thank you for patience while we continue working on this issue.

May 26, 08:32 PDT
Update - Some customers will start seeing their CloudHub 2.0 applications coming back online, we are verifying all deployments and progressing on making available all impacted applications.
This issue only impacted the CloudHub 2.0 shared space in the us-east-2 (Ohio) region.

Thank you for your patience while we continue working on restoring the applications.

May 26, 07:34 PDT
Update - While we continue working on redeploying the inaccessible applications we are doing validations, this is adding some extra time at the top of the redeployments, we will send a new update in the next 2 hours.

We appreciate your patience while we work on restoring the affected applications

May 26, 05:32 PDT
Update - We are now redeploying the inaccessible applications in order to return them to their normal operating state. This is a time consuming process and will continue for some time, we will post another update in approximately 2 hours.

We continue to work diligently to restore all of the inaccessible applications to their normal operating state.

Thank you

May 26, 03:21 PDT
Update - We have made a proactive communication via email to potentially impacted users.

Our team is continuing to work diligently and have a path to return the remaining inaccessible applications to their normal operating state.

Thank you for your support while we continue to address this issue.

May 26, 02:26 PDT
Update - The inaccessible applications have been fully identified and data has been restored, we are now in the process of building out and relaunching the inaccessible applications. This will take sometime and we will update you on our progress in approximately one hour.

Thank you again for your patience as we get the inaccessible applications back to their normal operational state.

May 26, 01:31 PDT
Update - As we continue our ongoing efforts to restore the us-east-2(Ohio), we want to call out that our suggested work-around does require that you understand your applications behavior. We are working to return the currently inaccessible apps to their working state. Once this is done, if you have launched your app in another region both applications may be running at the same time. The impact of this can only be evaluated by your staff. Please take this into consideration going forward.

In our previous update where we referenced creating a support case, if warranted by your business impact please make that an S1 case.

We appreciate your patience as we continue to work to restore the inaccessible applications

May 26, 00:19 PDT
Update - We are continuing our efforts to return the inaccessible applications to their normal operating state. If you are impacted and a Titanium or Platinum customer with global deployment you can deploy your applications to another region, if your architecture allows it. For Gold customers if your business is impacted you will need to create a support case referencing incident-52198963 and our support staff will work to change your default region to a workable option for you.

Thank you for your patience as our staff continues their work.

May 25, 23:26 PDT
Identified - The issue with the CloudHub 2.0 shared space in the us-east-2 (Ohio) region has been identified. Unfortunately, a subset of customer applications is currently inaccessible. Rest assured, we are actively working on resolving the issue and bringing the impacted applications back to their normal operating state.
May 25, 21:48 PDT
Investigating - We are currently investigating an issue with CH2.0 shared spaces in us-east-2
May 25, 19:45 PDT
May 25, 2023
May 24, 2023

No incidents reported.

May 23, 2023

Unresolved incident: AKS and RTF Interoperability issue.

May 22, 2023

No incidents reported.

May 21, 2023

No incidents reported.

May 20, 2023

No incidents reported.

May 19, 2023

No incidents reported.

May 18, 2023

No incidents reported.

May 17, 2023
Resolved - As of 13:19 (PT) the issue has been resolved. We will be providing an RCA via our support portal in the next 5 business days.
May 17, 14:15 PDT
Monitoring - Engineering teams have implemented a fix and we are monitoring the services.
May 17, 12:17 PDT
Investigating - Customers will experience Runtime Manager not loading. Our teams are investigating.
May 17, 10:02 PDT