Mendix Portal Hotfix
Timeline · 2 updates
- identified Dec 24, 2025, 10:59 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Dec 24, 2025, 10:59 AM UTC
This incident has been resolved.
Mendix had 47 outages in the last 2 years totaling 1347h 4m of downtime — averaging 1.9 incidents per month.
There were 47 Mendix outages since September 3, 2025 totaling 1347h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating an issue with Webhook Portal's Test Webhook functionality. Customers may experience degraded performance. This incident will be updated in 1 hour, or as events warrant.
We are continuing to investigate this issue.
We are continuing to investigate issue with Webhook Portal's degraded performance
We are continuing to investigate issue with Webhook Portal's degraded performance
We are continuing to investigate this issue.
Webhooks functionality is working as expected now. However, some customers are getting errors while testing the webhook through test Webhook functionality.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating an incident with pipelines component. Customers may experience slow responses This incident will be updated in 1 hour, or as events warrant.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We noticed a strange behavior in Academy, only taking an exam is affected. We are currently investigating the issue.
The incident has been identified and resolved.
We are currently experiencing reduced performance and increased error rates in Mendix Cloud EU: AWS Frankfurt 2. The teams are working on resolving it.
The issue has been identified and a fix is being implemented.
A fix has been implemented, and we see a decrease in error rates. We will keep monitoring the issue, and later share an explanation of the situation and how we will do better in the future. Apologies for the problems this has caused.
This incident has been resolved.
For older operator versions(below 2.24.0), we are facing an issue where the Private cloud apps are converting to Trial mode
We have identified the fix and currently working on deploying the fix in the Mendix on Kubernetes Portal.
We are continuing to work on a fix for this issue.
The fix is available. We have added a new option "Enable Fallback License" in the Environment details page. By default, its disabled. You can enable this feature, only when you have operator 2.24.0 and above. Once enabled, If an environment fails to communicate with the licensing server, it will use the fallback license instead of switching into Trial mode.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have observed missing list of components for the build packages. The team is busy working on a fix.
Incident has been resolved. Components should be available again for all users.
We've identified an issue impacting DNS resolution in a subset of our clusters. Our team are currently working with the highest priority to investigate the root cause and implement a fix.
Our teams have identified the issue and are currently working on a fix. At this moment only custom domains are affected, so we advise not to change custom domains for environments.
We're pleased to inform you that our engineering teams have successfully implemented a fix for the DNS resolution issue we've been experiencing. We are now actively monitoring our systems to ensure full restoration of service and stability across all affected areas. We sincerely apologize for any disruption, inconvenience, or impact on your operations caused by this incident. We truly appreciate your patience and understanding as we navigated these challenges.
Following our last update, continuous monitoring has shown no recurrence of issues related to the DNS issues. This incident is now resolved. We appreciate your patience and understanding throughout this process.
We observed a performance degradation for Software Composition. New package builds are currently experiencing delays in processing and appearing in Software Composition
This incident has been resolved.
With the October 14 update of Windows 11, Studio Pro 9, 10, and 11 can show errors in different panels and editors making it unusable. When you see the message "Hmmm... can't reach this page" with an error code of `ERR_CONNECTION_RESET`, in a tool panel or editor, your workstation is likely affected. Example panels where it can occur are the design properties and toolbox. Example editors are the Microflow, Nanoflow and Rule editor. The current known workarounds for this problem are: - Install "Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.439.210.0)" or - Uninstall the following Windows updates: KB5066835, KB5066131, and KB5065789 We are actively investigating this issue and will update regularly.
The current solution to this issue is to install "Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.439.210.0)". This has solved current running incidents, but we are narrowly monitoring this with our customers to make sure all issues are resolved.
After closely monitoring the issue with existing customers and new incidents, we can confirm that the latest patches from Microsoft resolved the issue that was introduced.
We have observed some degradations in processing of new build packages for Software Composition both from Control Center & Developer Portal view. The team is currently investigating.
This incident has been resolved.
We are currently investigating issues with logging service in Mendix Cloud Middle East (Bahrain)
The logging service is back up and we're monitoring the results. Today's logs for all applications in Mendix Cloud Middle East (Bahrain) region are affected.
Yesterday's logs for impacted applications have been recovered and the incident has been resolved.
We are currently observing issues where some free apps are unable to resume due to a recent change in an internal platform component. Our team has identified the root cause & working on a fix. In the meantime, if your app fails to resume, we recommend redeploying it to make it active again. We will provide updates as more information becomes available. Thank you for your patience and understanding.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We identified an issue in Self-service "Entitlements" (Control Center tab) and will deploy a hotfix to address it. During this maintenance window Self-service "Entitlements" (Control Center tab) will be unavailable for about 15 minutes.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are aware that some users are experiencing errors when viewing Live Logs from the Environments page in the Mendix Portal. Our team is currently investigating the issue. Please note that Live Logs remain available and fully functional from the Logs page.
We are continuing with our investigation. We've identified that deploying or re-deploying apps on our Cloudfoundry platform may result in missing metrics and false heartbeat alerts. If your app's platform shows as Cloudfoundry on the Mendix Portal, please refrain from new deployments. Our team is actively working on a resolution.
We're continuing to investigate the issue. We have also identified impact on the backups downloads functionality for Mendix applications
We're continuing to investigate the issue. We can conclude that backups downloads are not impacted.
A fix is being prepared and will be deployed later today.
A fix has been implemented and we're monitoring the results.
This incident has been resolved. Live logs are accessible from the environments page. Metrics are also available again. We won't be able to retrieve missing metrics for the impacted apps. We apologize for the inconvenience this may have caused.
We are currently experiencing issues with the build process that are preventing Mendix app deployments to Kubernetes. The root cause is an authentication failure stemming from a partial service disruption at Docker Hub.
We are now observing successful requests to Docker Hub, and deployments are proceeding as expected. The incident will remain in monitoring while we continue to verify stability.
This incident has been resolved.
We are currently experiencing gaps in metrics and logs for all Mendix Cloud regions, specifically affecting applications on the Kubernetes platform. The issue has been identified, and our teams are actively working on deploying a fix.
The issue has been fixed and we are actively monitoring the system.
Our engineers have confirmed the fix is stable and have no longer observed gaps or missing loglines since 12:50 UTC. Issues started to occur around 12:05 UTC. During this period there might be gaps in the application graphs and missing loglines.
We are currently experiencing gaps in container metrics for the Frankfurt region, specifically affecting applications on our Kubernetes platform. The issue has been identified, and our teams are actively working on deploying a fix. We will provide an update once resolved.
Our teams are currently finalizing the fix and conducting tests. We anticipate releasing the resolution soon and will provide an update upon completion.
The fix for the container metrics gaps in the Frankfurt region (Kubernetes applications) has been released, and we are actively monitoring the system. While new metrics are now reporting correctly, previously missing historical metrics are not yet restored. Our teams are currently investigating the possibility of recovering these missing metrics, and we will provide an update on this effort.
Our teams have confirmed the fix is stable, and we are no longer observing any related anomalies in our logs. New metrics are reporting correctly. We appreciate your patience and understanding throughout this incident.
We have identified an issue affecting the creation of deployment packages. In a small number of cases the build process is unable to reach the repository service. Our team has pinpointed the root cause and is actively working on a permanent fix. In the meantime, retrying the build typically results in a successful deployment package.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing an issue with GenAI Resources and are working to resolve the situation. Our apologies.
We experienced a DNS service interruption from 10:35 - 12:00 UTC on September 9, 2025. This disruption affected both the generation of new GenAI resource keys and the use of existing ones in this region. The issue has been resolved, and all DNS services are now operating normally. We are investigating the root cause of this service interruption and implementing measures to prevent such occurrences in the future.