Looking for an update now? Check the current status, or follow Mendix Technology for future changes.
43.1%of 51 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
18.5%
27
22
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Mendix Cloud US-EastMendix Cloud EU (Frankfurt)Mendix Cloud Asia Pacific (Tokyo)Mendix Cloud Dedicated US-West EchoMendix Cloud Dedicated UK EchoMendix Cloud UKMendix Cloud Dedicated Asia Pacific (Singapore) EchoMendix Cloud IEMendix Cloud Dedicated US-East HotelMendix Cloud Dedicated US-East MikeMendix Cloud US-WestMendix Cloud Dedicated US-East PapaMendix Cloud Asia Pacific (Sydney)Mendix Cloud Dedicated EU (Frankfurt) SierraMendix Cloud Canada (Central)Mendix Cloud Dedicated EU (Frankfurt) UniformMendix Cloud Asia Pacific (Singapore)Mendix Cloud Dedicated Asia Pacific (Singapore) AbleMendix Cloud Dedicated US-East KiloMendix Cloud Asia Pacific (Mumbai)Mendix Cloud Africa (Cape Town)Mendix Cloud South America (São Paulo)Mendix Cloud EU (Frankfurt 2)Mendix Cloud Asia Pacific (Osaka)Mendix Cloud Asia Pacific (Seoul)Mendix Cloud Asia Pacific (Jakarta)
monitoring
A fix has been implemented and we're monitoring the results.
identified
We identified the impact to be on many more production clusters. Incident has been updated to reflect that. We're working on a fix.
investigating
We are currently investigating errors while accessing the logs page for some environments. So far, we've identified the impact on environments running on Mendix Cloud US-East, Mendix Cloud EU and Mendix Cloud EU (Frankfurt 2).
Mendix Cloud US-EastMendix Cloud EU (Frankfurt)Mendix Cloud Asia Pacific (Tokyo)Mendix Cloud Dedicated US-West EchoMendix Cloud Free Tier EUMendix Cloud Dedicated UK EchoMendix Cloud UKMendix Cloud Dedicated Asia Pacific (Singapore) EchoMendix Cloud IEMendix Cloud Dedicated US-East HotelMendix Cloud Dedicated US-East MikeMendix Cloud US-WestMendix Cloud Dedicated US-East PapaMendix Cloud Asia Pacific (Sydney)Mendix Cloud Dedicated EU (Frankfurt) SierraMendix Cloud Canada (Central)Mendix Cloud Dedicated EU (Frankfurt) UniformMendix Cloud Asia Pacific (Singapore)Mendix Cloud Dedicated Asia Pacific (Singapore) AbleMendix Cloud Dedicated US-East KiloMendix Cloud Dedicated US-East CharlieMendix Cloud Asia Pacific (Mumbai)Mendix Cloud Dedicated US-East ColinMendix Cloud Dedicated EU (Frankfurt) MetroMendix Cloud Africa (Cape Town)Mendix Cloud South America (São Paulo)Mendix Cloud EU (Frankfurt 2)Mendix Cloud Asia Pacific (Osaka)Mendix Cloud Asia Pacific (Seoul)Mendix Cloud Asia Pacific (Jakarta)Mendix Cloud EU (Frankfurt): GenAI ResourcesMendix Cloud Canada (Central): GenAI Resources
monitoring
The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.
What you need to do
If your app is running on Java 11, 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
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. 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.
identified
The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.
identified
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, Java 21 and Java 17. These new versions include the critical patch updates.
For Java 11, 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 17, 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, 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.
Security update: compromised eMudhra certificates blocked for Mendix Cloud apps
Mendix Cloud US-EastMendix Cloud EU (Frankfurt)Mendix Cloud Asia Pacific (Tokyo)Mendix Cloud Dedicated US-West EchoMendix Cloud Free Tier EUMendix Cloud Dedicated UK EchoMendix Cloud UKMendix Cloud Dedicated Asia Pacific (Singapore) EchoMendix Cloud IEMendix Cloud Dedicated US-East HotelMendix Cloud Dedicated US-East MikeMendix Cloud US-WestMendix Cloud Dedicated US-East PapaMendix Cloud Asia Pacific (Sydney)Mendix Cloud Dedicated EU (Frankfurt) SierraMendix Cloud Canada (Central)Mendix Cloud Dedicated EU (Frankfurt) UniformMendix Cloud Asia Pacific (Singapore)Mendix Cloud Dedicated Asia Pacific (Singapore) AbleMendix Cloud Dedicated US-East KiloMendix Cloud Dedicated US-East CharlieMendix Cloud Asia Pacific (Mumbai)Mendix Cloud Dedicated US-East ColinMendix Cloud Dedicated EU (Frankfurt) MetroMendix Cloud Africa (Cape Town)Mendix Cloud South America (São Paulo)Mendix Cloud EU (Frankfurt 2)Mendix Cloud Asia Pacific (Osaka)Mendix Cloud Asia Pacific (Seoul)Mendix Cloud Asia Pacific (Jakarta)Mendix Cloud EU (Frankfurt): GenAI ResourcesMendix Cloud Canada (Central): GenAI Resources
monitoring
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.
Mendix Cloud EU (Frankfurt)Mendix Cloud Dedicated EU (Frankfurt) SierraMendix Cloud Dedicated EU (Frankfurt) UniformMendix Cloud Dedicated EU (Frankfurt) MetroMendix Cloud EU (Frankfurt 2)
monitoring
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.
investigating
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 and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
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.
Mendix Cloud UKMendix Cloud Asia Pacific (Mumbai)Mendix Cloud EU (Frankfurt 2)
monitoring
We have implemented a fix and are monitoring the results.
Resizes can be resumed on all affected regions.
identified
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.
identified
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.
identified
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.
identified
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)
identified
We have identified another region where we experience a reduced capacity of database resources.
Following plans are affected:
- M21(standard/premium)
- XXXL(standard/premium)
identified
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.
Mendix Cloud US-EastMendix Cloud EU (Frankfurt)Mendix Cloud Asia Pacific (Tokyo)Mendix Cloud Dedicated US-West EchoMendix Cloud Dedicated UK EchoMendix Cloud UKMendix Cloud Dedicated Asia Pacific (Singapore) EchoMendix Cloud IEMendix Cloud Dedicated US-East HotelMendix Cloud Dedicated US-East MikeMendix Cloud US-WestMendix Cloud Dedicated US-East PapaMendix Cloud Asia Pacific (Sydney)Mendix Cloud Dedicated EU (Frankfurt) SierraMendix Cloud Canada (Central)Mendix Cloud Dedicated EU (Frankfurt) UniformMendix Cloud Asia Pacific (Singapore)Mendix Cloud Dedicated Asia Pacific (Singapore) AbleMendix Cloud Dedicated US-East KiloMendix Cloud Dedicated US-East CharlieMendix Cloud Asia Pacific (Mumbai)Mendix Cloud Dedicated US-East ColinMendix Cloud Dedicated EU (Frankfurt) MetroMendix Cloud Africa (Cape Town)Mendix Cloud South America (São Paulo)Mendix Cloud EU (Frankfurt 2)Mendix Cloud Asia Pacific (Osaka)Mendix Cloud Asia Pacific (Seoul)Mendix Cloud Asia Pacific (Jakarta)
investigating
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.
investigating
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.
investigating
We are getting reports from customers who are experiencing performance degradation of their application after its database was upgraded to a higher PostgreSQL version.
Metrics and Alerts for impacted applications are available again. We'll keep monitoring the results.
investigating
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.
Legacy Incident Archive
27 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
Developer Portal reduced functionality
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We've identified an issue with application metrics in Mendix Cloud EU (Frankfurt 2) which resulted in incorrect runtime heartbeat alert emails sent to customers. We've implemented a fix and are monitoring the results. The metrics are missing from 27 April 1725 CEST until 28 April 1300 CEST and won't be recoverable. We apologize for the inconvenience caused.
Developer Portal Sign-Up Outage
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We’re currently experiencing an issue that is preventing new users from signing up to the Developer Portal.
Our engineering team has identified the root cause and is actively working on a fix. Existing users can continue to access and use the portal without interruption.
We’ll share further updates as progress is made. Thank you for your patience.
File Storage Access Disruption — Multiple Regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix for the file storage access issue has been rolled out across all affected regions. We are now monitoring the situation.
If your application is still experiencing file storage errors, please restart or redeploy your environment without Zero Downtime deployment (ZDT).
We will continue monitoring and provide a final update once we have confirmed full resolution.
identified
We have identified the root cause of the file storage access disruption.
A fix has been prepared and is currently being rolled out. Due to the number of affected regions, the rollout may take some time to propagate across all environments. Applications should gradually regain full file storage access as the fix is applied to ...
identified
We have identified the issue and are working on a fix.
Next update: We will provide an update within 30 minutes.
investigating
We are currently investigating an issue affecting file storage operations across multiple Mendix Cloud environments. Affected applications may experience errors when uploading or downloading files.
Impact: Applications may be unable to read or write files stored in the platform's object storage.
Affected regions: Multiple Mendix Cloud regions are impacted. We are assessing the full scope.
Our engineering team is actively investigating the root cause and working toward a resolution. No data ...
Mendix Portal partial outage
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating an issue with Mendix Portal. Customers are unable to use AI log Summary feature for Mendix Pipelines Run details.
Mendix Cloud Deployment degraded performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the issue and implemented a fix.
We are closely monitoring the fix.
investigating
We are investigating an incident with Mendix deployments across all regions. Customers may experience application startup failures and deployment errors when their application model contains log nodes with special characters (quotes, umlauts, or non-ASCII characters).
Customers can temporarily resolve the problem by renaming log nodes in Mendix Studio Pro to use only ASCII characters (A-Z, a-z, 0-9, underscore, hyphen, space) and redeploying.
This incident will be updated as events warrant.
A fix has been implemented and we are monitoring the results.
identified
The Developer Profiles app relies on a microservice that forwards user activity to be displayed on the profiles. Due to an infrastructure change, the cluster hosting this microservice was decommissioned. As a result, user activity is not being reflected in Developer Profiles. Existing profile data remains intact, but no new updates will appear until the issue is resolved.
March 2026
Incident in Middle East (UAE) region
criticalSource not attested
Last archived state: resolved
View archived record details
identified
The situation hasn't changed. We have seen no improvement in affected services.
The vendor is working hard to restore their services, but didn't provide an ETA when services are restored.
Expect Next Update: We will only update again if there is actually an update. Subscribe to get updates automatically.
identified
The situation hasn't changed. We have seen no improvement in affected services.
The vendor is working hard to restore their services, but didn't provide an ETA when services are restored.
Expect Next Update: Friday March 20th 2026
identified
The situation hasn't changed. We have seen no improvement in affected services.
The vendor is working hard to restore their services, but didn't provide an ETA when services are restored.
Expect Next Update: Monday March 16th 2026, 15:00 UTC
identified
The situation hasn't changed. We have seen no improvement in affected services.
The vendor is expecting recovery to take at least another day.
Expect Next Update: Friday March 13th 2026, 15:00 UTC
identified
The situation hasn't changed. We have seen no improvement.
The vendor is expecting recovery to take at least another day.
We will update the incident as events warrant.
identified
The situation hasn't changed. We have seen no improvement.
The vendor is expecting recovery to take at least another day.
We will update the incident as events warrant.
identified
The situation hasn't changed. We have seen no improvement.
The vendor is expecting recovery to take at least another day.
We will update the incident as events warrant.
identified
We have identified an issue with an upstream vendor due to a regional incident, causing most applications in that region to be unavailable.
The vendor is expecting recovery to take at least another day.
We will update the incident as events warrant.
identified
We have identified an issue with an upstream vendor due to a regional incident, causing most applications in that region to be unavailable.
We will update the incident as events warrant.
identified
Due to a power outage in the data center where the standard plan applications are running, unfortunately those applications are inaccessible.
investigating
We are investigating an incident in the Middle East (UAE) region. Customers may experience problems when trying to access their applications.
