Mendix outage history

What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps. Who is affected All customers with applications running on Mendix Cloud. What we did We have updated the Java version for Java 25 and Java 21. These new versions include the critical patch updates. We're working on updating the other Java versions used on Mendix Cloud (Java 11, Java 17). For these Java versions, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud. What you need to do If your app is running on Java 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough! We recommend doing this in your usual order, so you can check that your applications still work before updating production: 1. Test environment 2. Acceptance environment 3. Production environment If your app is running on Java 11 or Java 17, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions. Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly. If you have any questions, feel free to contact support.

What happened A certificate authority called eMudhra generated the cryptographic keys for eight of its intermediate certificates incorrectly, that caused the certificates to become compromised. Java, which Mendix apps run on, trusted these certificates by default. Someone able to intercept an app's outgoing connection could pose as the server it was calling. Who is affected Only the outgoing connections your app makes over HTTPS, for example REST or web service calls, or other integrations with external systems. Traffic coming in to your app, such as users opening it in a browser, is not affected. What we did We have updated the Mendix Cloud build process so that apps built from now on no longer trust the compromised certificates. We have also updated the underlying OS base image. This was released on 22 Oct at 17:30 UTC. What you need to do The fix is added when your app is deployed, so apps that are already running only get it when you redeploy. You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough! If your app makes outgoing calls to other systems, please redeploy it. We recommend doing this in your usual order, so you can check that your integrations still work before production: 1. Test environment 2. Acceptance environment 3. Production environment If your app does not make outgoing calls, no action is needed. It will receive the update at its next regular deployment. Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly. What to expect after redeploying If one of the systems your app calls uses a certificate issued by one of the affected eMudhra authorities, the connection will now fail. In that case, ask the owner of that system to replace its certificate. If you have any questions, feel free to contact support.

Automated nightly backups for some environments in Mendix Cloud EU (Frankfurt) and Mendix Cloud EU (Frankfurt 2) were unavailable on 19 October and 20 October. We executed a platform maintenance on 21 October to resume the backups service and create fresh backups. Affected environments will see missing backups for 19 October and 20 October. We apologize for the inconvenience caused by this.

We have identified reduced capacity of database resources this will impact the following actions: - provisioning a new application environment - clearing a database - downsizing The following plans are affected: - M21(standard/premium) - S21(standard/premium) We are investigating a solution, we will update this incident as events warrant.

A fix has been implemented for the reduced capacity of database resources. Provisioning new application environments, clearing a database, and downsizing are working again. We are monitoring the situation.  If one of your environments is still affected, please contact Mendix Support.

This incident has been resolved. We haven't noticed any issues related to the reduced capacity of database resources, after implementing the fix. If you still experience problems related to this incident, reach out to support.

We have identified an issue because of which the package builds are failing sometimes.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating a platform incident with Free Apps. Customers may experience failures during free app deployments and resuming their apps. This incident will be updated in 1 hour, or as events warrant.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have identified a reduced capacity of database resources for the following Mendix plan: - XXXL(standard/premium) We advise customers not to resize to the mentioned plan, until further notice.

We have identified another region where we experience a reduced capacity of database resources. Following plans are affected: - M21(standard/premium) - XXXL(standard/premium)

We have identified another region where we experience a reduced capacity of database resources. Following plans are affected: - L21(standard/premium) - M21(standard/premium) - XXXL(standard/premium)

We have identified another region where we experience a reduced capacity of database resources. Following plans are affected: - L21(standard/premium) - M21(standard/premium) - S21(standard/premium) - XXXL(standard/premium) Our engineering teams are working on a permanent solution.

We have identified another region where we experience a reduced capacity of database resources. The reduced capacity of database resources does not affect functionality of current databases, but it affects creation of new databases. Following plans are affected: - L21(standard/premium) - M21(standard/premium) - S21(standard/premium) - XXXL(standard/premium) Our engineering teams are working on a permanent solution.

The issue with creating new databases has been resolved. Existing databases and new database creation are now operating normally. However, upgrading existing databases on the following plans in the listed regions remains affected by reduced database resource capacity: - L21 (standard/premium) - M21 (standard/premium) - S21 (standard/premium) - XXXL (standard/premium). Our engineering teams continue to work on a permanent solution and will provide further updates as progress is made.

We have implemented a fix and are monitoring the results. Resizes can be resumed on all affected regions.

The incident is resolved. We haven't noticed any new issues related to the reduced capacity of database resources.

We are getting reports from customers who are experiencing performance degradation of their application after its database was upgraded to a higher PostgreSQL version.

We are getting reports from customers who are experiencing performance degradation of their application after its database was upgraded to a higher PostgreSQL version. Based on the reports we received we have decided to postpone the PostgreSQL17 maintenance until further notice.

We are continuing to investigate the issue. We have determined that currently no more than 0.07% of deployed environments are affected, and customers of those affected environments are already in contact with our Support dept. As mentioned in the previous update; we have decided to postpone the PostgreSQL maintenance until further notice. Customers for whom the maintenance was postponed will be notified no less than 2 weeks in advance before maintenance will be resumed.

This incident is resolved. A workaround is available for the performance degradation reported after the PostgreSQL upgrade. Our Support department is in direct contact with each affected customer. As previously communicated, the platform-wide PostgreSQL 17 maintenance remains postponed until further notice. Customers whose maintenance was postponed will be notified no less than two weeks in advance before it is resumed. There is no platform-wide impact, and all components have been returned to operational.

We are currently investigating issue with metrics availability in some production clusters. Impacted applications will see 'No data' on the metrics page and will not trigger any alerts. We will update the incident when we have more information.

Metrics and Alerts for impacted applications are available again. We'll keep monitoring the results.

This incident has been resolved.

We are investigating an issue with Mendix Portal. Customers may experience problems accessing and managing their projects. This incident will be updated in 1 hour, or as events warrant.

We are continuing to work on a fix for this issue.

The production environment of projects.home.mendix.com has been restarted and we are monitoring the results.

The incident has been resolved.

Between 10:04 UTC and 20:00 UTC on August 21, applications in this dedicated cluster were unable to establish connections to other applications in the same dedicated cluster. Applications that depend on data provided by another application may have been unavailable to end users during this period. The cause was identified in the platform network configuration and a fix has been applied. Connectivity between applications has been restored and confirmed. No action is required from customers, and it was not necessary to restart or redeploy applications. If you continue to experience any problems, please contact Mendix Support.

We are noticing intermittent issues with our Mendix Portal. We are investigating the issue. We will update the incident as events warrant.

We are currently investigating intermittent connection issues with Mendix Portal. Customers are advised not to restart or deploy their applications. We will update the incident when we have more information.

We are still investigating intermittent connection issues with Mendix Portal. Customers are advised not to restart or deploy their applications. We will update the incident when we have more information. Scheduled (planned) PostgreSQL 17 upgrade maintenances have been postponed due to this incident and will be rescheduled, most likely next week.

A fix has been implemented and we're monitoring the results.

The issue has resurfaced, we're continuing our investigation of intermittent connection issues with Mendix Portal. Customers are advised not to restart or deploy their applications. We will update the incident when we have more information.

We have found the cause of the incident and implemented a fix. We are currently monitoring the results. Customers can resume restarting or deploying their applications from the Mendix Portal.

After implementing a fix and monitoring the results closely, we noticed the Mendix Portal functionality resumed back to normal. Therefore we will close the incident. As mentioned in one of our updates scheduled (planned) PostgreSQL 17 upgrade maintenances will be rescheduled. If you continue to experience any problems, please contact Mendix Support.

Maintenances have been cancelled due to platform instability. Any environment that experienced a cancelled maintenance can be operated normally. Some of the environments are experiencing high database load. This is due to failed optimization tasks during the maintenance. We are in the process of rescheduling them. Performance should return to normal after they have been executed.

We are investigating an incident with deployments. Customers may experience failed deployments. This incident will be updated in 1 hour, or as events warrant.

We have identified the issue. We notice intermittent network issues with an external package store. Impacted customers can retry their deployment. This incident will be updated in 12 hours, or as events warrant.

The external package store has recovered and is now operating normally. We are continuing to monitor the system to confirm full stability.

The incident has been resolved.

We are continuing to investigate the issue.

We are investigating a platform incident with Free Apps. Customers may experience intermittent failures during free app deployments. This incident will be updated in 1 hour, or as events warrant.

The issue has been identified. We're planning to release this fix on 29 Jul at 1500 UTC as a hotfix.

The hotfix has been released and free apps deployments are working again. We'll continue to monitor the results.

This incident has been resolved.

We are investigating an issue with Mendix Portal where customers may experience issues with uploading backups. This incident will be updated in 1 hour, or as events warrant.

The issue has been identified and we're working on a fix. We will provide updates as more information becomes available.

The fix is taking longer than expected. We're planning to release this fix on 29 Jul at 1500 UTC as a hotfix. Unfortunately we cannot offer any workaround for uploading backups until the fix is released and we apologize for the inconvenience caused by this issue.

The hotfix has been deployed and we're monitoring the results. Impacted customers can upload backups again.

This incident has been resolved.

We are investigating an incident with custom domains being unavailable after restarting the environment. Customers may experience: - The application being unavailable on the custom domain - Custom domains not shown on Mendix Portal We advise customers with a custom domain on their application to not restart or deploy to those applications for the time being. This incident will be updated in 1 hour, or as events warrant.

We are continuing to investigate this issue.

A fix has been implemented. Restarting the application environment recovers the custom domains. We will continue to monitor the results.

This incident has been resolved.

We are currently investigation issue.

Issue was identified as a problem with the cleanup of Old SBOMs.

Fix is applied and we will monitor the performance.

Incident has been resolved.

[RCA 006 - SBOM Server RDS CPU saturation & connection-pool exhaustion - Control Center \(Cloud\)](https://mendix.atlassian.net/wiki/spaces/CCC1/pages/4923031817/RCA+006+-+SBOM+Server+RDS+CPU+saturation+connection-pool+exhaustion)

We are currently experiencing issues with deployments in our Mendix Cloud EU: Frankfurt 1 and Frankfurt 2 region. Multiple deployments are failing at this time. Please do not attempt to deploy applications to Frankfurt 1 or Frankfurt 2 regions until this issue is resolved. We are aware of this issue and our team is actively investigating. We will provide updates as more information becomes available.

Additional Impact Identified: Some environments in Mendix Cloud EU- Frankfurt 1 and Frankfurt 2 have experienced unexpected restarts. We are investigating whether this is related to the deployment failure issue.

We have identified the issue also impacts Mendix Cloud US-East and Mendix Cloud Dedicated EU (Frankfurt) Sierra regions. We have identified the root cause of the deployment failures and unexpected environment restarts affecting multiple regions.

We are currently applying fixes to the underlying servers where the issue was identified. As part of this remediation, some environments may restart while we are fixing the issue, these restarts are expected and necessary to resolve the problem. Please continue to avoid new deployments until we confirm the fix is complete.

As we continue to fix the underlying platform, we have prioritized production environments to minimize impact. Deployment errors have significantly decreased as the fixes are being applied. We are continuing to work towards complete recovery and will provide an update once all systems are fully restored.

All production applications in the impacted regions are now up and running without issues. We are currently working to resolve the remaining non-production environments, and redeployments are functioning normally again. We will continue monitoring and provide a final update once all environments are fully restored.

The incident has been fully resolved and deployments and restarts are functioning as expected. Some non-production environments are currently in a failed state - as a workaround, please restart or redeploy these environments which will resolve the issue. We are working on automated recovery for the remaining affected environments and will continue monitoring to ensure stability.

This incident is now closed. The platform has remained stable with no new issues reported. All production and non-production environments are operating normally in the impacted regions. Please reach out to Mendix Support in case you continue to experience any issues with your applications or environments. Thank you for your patience throughout this incident.