Mendix Outage History

Started May 12, 2026, 04:49 PM UTC· resolved May 15, 2026, 07:03 AM UTC

1. investigating May 12, 2026, 04:49 PM UTC

   We are currently investigating the issue.

2. identified May 12, 2026, 05:19 PM UTC

   We identified the root cause. The team is working on solving the problem.

3. monitoring May 12, 2026, 05:56 PM UTC

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

4. resolved May 15, 2026, 07:03 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 09, 2026, 01:30 AM UTC· resolved May 09, 2026, 02:43 AM UTC

1. investigating May 09, 2026, 01:30 AM UTC

   We are currently investigating an issue affecting access to Mendix Portal via sprintr.home.mendix.com. Customers may experience browser security warnings or be unable to access the service through this URL. At this time, the issue appears to be related to the SSL/TLS certificate presented for this domain. We are working to restore normal access as quickly as possible and will provide an update as soon as more information is available. As a temporary workaround, customers can access the service using: projectservice.mendix.com Mendix Cloud deployment and monitoring services are not affected and remain fully operational via cloud.home.mendix.com.

2. monitoring May 09, 2026, 02:40 AM UTC

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

3. resolved May 09, 2026, 02:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 12:52 PM UTC· resolved May 08, 2026, 04:03 PM UTC

1. investigating May 08, 2026, 12:52 PM UTC

   We will be applying a security hotfix to our infrastructure across all Mendix Cloud regions this afternoon. No application restarts are required and no customer impact is expected.

2. monitoring May 08, 2026, 03:53 PM UTC

   We have applied a security hotfix to our infrastructure in all Mendix Cloud regions. We continue to monitor the systems.

3. resolved May 08, 2026, 04:03 PM UTC

   Our clusters continue to operate without any disruption after the hotfix was applied.

Read the full incident report →

Started Apr 28, 2026, 12:21 PM UTC· resolved Apr 28, 2026, 02:36 PM UTC

1. identified Apr 28, 2026, 12:21 PM UTC

   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.

2. monitoring Apr 28, 2026, 12:21 PM UTC

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

3. resolved Apr 28, 2026, 02:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 09:34 AM UTC· resolved Apr 27, 2026, 01:38 PM UTC

1. identified Apr 27, 2026, 09:34 AM UTC

   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.

2. monitoring Apr 27, 2026, 10:55 AM UTC

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

3. resolved Apr 27, 2026, 01:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 05:13 PM UTC· resolved Apr 22, 2026, 06:59 PM UTC

1. investigating Apr 22, 2026, 05:13 PM UTC

   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 has been lost — existing files remain intact. Next update: We will provide an update within 30 minutes.

2. identified Apr 22, 2026, 05:38 PM UTC

   We have identified the issue and are working on a fix. Next update: We will provide an update within 30 minutes.

3. identified Apr 22, 2026, 05:57 PM UTC

   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 each region. Existing files and data remain unaffected. Next update: We will provide another update once the rollout is complete.

4. monitoring Apr 22, 2026, 06:17 PM UTC

   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.

5. resolved Apr 22, 2026, 06:59 PM UTC

   The file storage access disruption has been resolved. We have confirmed that no new applications are being affected. If your application is still experiencing file storage errors, please restart or redeploy your environment without Zero Downtime deployment (ZDT). If the issue persists after restarting, please contact our support team for further assistance.

Read the full incident report →

Started Apr 03, 2026, 02:50 PM UTC· resolved Apr 13, 2026, 07:20 AM UTC

1. investigating Apr 03, 2026, 02:50 PM UTC

   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.

2. monitoring Apr 08, 2026, 02:23 PM UTC

   We have identified the issue and implemented a fix. We are closely monitoring the fix.

3. resolved Apr 13, 2026, 07:20 AM UTC

   We haven't seen new issues related to this incident. The incident is resolved.

Read the full incident report →

Started Apr 02, 2026, 09:12 AM UTC· resolved May 18, 2026, 08:43 AM UTC

1. identified Apr 02, 2026, 09:12 AM UTC

   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.

2. monitoring May 06, 2026, 11:24 AM UTC

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

3. resolved May 18, 2026, 08:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 25, 2026, 01:02 PM UTC· resolved Mar 25, 2026, 03:42 PM UTC

1. investigating Mar 25, 2026, 01:02 PM UTC

   We are currently investigating an issue causing app deployments to fail. While we work on resolving this, please refrain from triggering new deployments. We will provide updates as the investigation progresses.

2. investigating Mar 25, 2026, 02:48 PM UTC

   We are continuing to investigate this issue. We will provide updates as the investigation progresses.

3. monitoring Mar 25, 2026, 03:04 PM UTC

   A fix has been implemented and we're monitoring the results. Customers might notice slower deployments until the incident is fully resolved.

4. resolved Mar 25, 2026, 03:42 PM UTC

   This incident has been resolved. We apologize for the inconvenience caused.

Read the full incident report →

Started Mar 17, 2026, 06:16 PM UTC· resolved Mar 17, 2026, 07:26 PM UTC

1. investigating Mar 17, 2026, 06:16 PM UTC

   We are investigating DNS issues that limit the mxapp (re)deployment capability. Only Mendix Cloud Dedicated EU (Frankfurt) Sierra is impacted. We advise customers in this region to refrain from redeploying until this issue is resolved.

2. monitoring Mar 17, 2026, 06:41 PM UTC

   The dedicated DNS server upon which we depend is working again, and we see a restoration of service in our cluster. Deployments are working again, and we'll keep monitoring the situation for the time being and watch for regressions. Customers are advised to redeploy if they were affected.

3. resolved Mar 17, 2026, 07:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 05:48 AM UTC· resolved May 20, 2026, 08:54 AM UTC

1. investigating Mar 02, 2026, 05:48 AM UTC

   We are experiencing some difficulties reaching the Middle East (Bahrain) region.

2. identified Mar 02, 2026, 08:21 AM UTC

   We have identified an issue with an upstream vendor due to a regional incident, causing applications in that region to be unavailable. Customers using the premium plan will not be affected. We will update the incident as events warrant.

3. identified Mar 02, 2026, 03:39 PM UTC

   We have identified an issue with an upstream vendor due to a regional incident, causing applications in that region to be unavailable. The vendor is working hard to restore their services, but didn't provide an ETA when services are restored. As mentioned in our previous message customers using the premium plan are not affected. We will update the incident as events warrant.

4. identified Mar 03, 2026, 03:53 PM UTC

   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. We will update the incident as events warrant.

5. identified Mar 04, 2026, 02:30 PM UTC

   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. As mentioned in our previous message, environments using a premium resource pack are not affected. We will update the incident as events warrant.

6. identified Mar 09, 2026, 09:15 AM UTC

   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. We will update the incident as events warrant.

7. identified Mar 10, 2026, 03:23 PM UTC

   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 13th 2026, 15:00 UTC

8. identified Mar 13, 2026, 03:28 PM UTC

   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

9. identified Mar 17, 2026, 09:48 AM UTC

   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

10. identified Mar 20, 2026, 02:52 PM UTC

    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.

11. identified Mar 27, 2026, 09:35 AM UTC

    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. NOTE: Do not stop/restart your environment if it is currently still active and available. This advice applies to customers on the Premium plan. Expect Next Update: We will only update again if there is actually an update. Subscribe to get updates automatically.

12. resolved May 20, 2026, 08:54 AM UTC

    The conditions in the Middle-East have not changed since the last update. We have migrated most of our customers' workloads to alternate regions and are not accepting new applications for the Middle-East. As a result, we are resolving the incident for this region.

Read the full incident report →

Started Mar 01, 2026, 04:06 PM UTC· resolved May 20, 2026, 08:53 AM UTC

1. investigating Mar 01, 2026, 04:06 PM UTC

   We are investigating an incident in the Middle East (UAE) region. Customers may experience problems when trying to access their applications.

2. identified Mar 01, 2026, 04:07 PM UTC

   Due to a power outage in the data center where the standard plan applications are running, unfortunately those applications are inaccessible.

3. identified Mar 02, 2026, 08:29 AM UTC

   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.

4. identified Mar 02, 2026, 03:43 PM UTC

   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.

5. identified Mar 03, 2026, 03:54 PM UTC

   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.

6. identified Mar 04, 2026, 02:33 PM UTC

   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.

7. identified Mar 09, 2026, 09:14 AM UTC

   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.

8. identified Mar 10, 2026, 03:24 PM UTC

   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

9. identified Mar 13, 2026, 03:28 PM UTC

   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

10. identified Mar 17, 2026, 09:49 AM UTC

    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

11. identified Mar 20, 2026, 02:52 PM UTC

    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.

12. resolved May 20, 2026, 08:53 AM UTC

    The conditions in the Middle-East have not changed since the last update. We have migrated most of our customers' workloads to alternate regions and are not accepting new applications for the Middle-East. As a result, we are resolving the incident for this region.

Read the full incident report →

Started Feb 12, 2026, 02:12 PM UTC· resolved Feb 12, 2026, 02:28 PM UTC

1. investigating Feb 12, 2026, 02:12 PM UTC

   We will be releasing a hotfix for Licensing Service. This fix will deliver an urgent update to increase stability of the service. During the short downtime some SAP and Private Cloud (connected) apps might get short-lived errors during the license validation.

2. identified Feb 12, 2026, 02:13 PM UTC

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

3. resolved Feb 12, 2026, 02:28 PM UTC

   The update has been released.

Read the full incident report →

Started Feb 06, 2026, 03:13 PM UTC· resolved Feb 24, 2026, 01:53 PM UTC

1. identified Feb 06, 2026, 03:13 PM UTC

   We have identified an issue in the region Mendix Cloud EU (Frankfurt). Customers sending email, using an SMTP relay over port 25, might be unable to deliver those e-mails. This issue is caused by one or more of our outgoing IP addresses being blocklisted by an external email security provider. We are in communication with the external email security provider to have the affected IP addresses removed from their list. Until then, our advice is to switch to a different SMTP relay provider and avoid using port 25 for sending email altogether.

2. identified Feb 11, 2026, 12:15 PM UTC

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

3. resolved Feb 24, 2026, 01:53 PM UTC

   This incident has been resolved. The affected outgoing IP addresses have been removed from the external email security provider's blocklist. Email delivery via SMTP relay from Mendix Cloud EU (Frankfurt) is operating normally again. As a general best practice, we recommend using port 587 (TLS) instead of port 25 for outgoing email. Please refer to our Sending Email documentation for recommended SMTP configuration: https://docs.mendix.com/developerportal/deploy/sending-email/#external-email-providers

Read the full incident report →

Started Jan 28, 2026, 11:25 AM UTC· resolved Feb 02, 2026, 09:32 AM UTC

1. investigating Jan 28, 2026, 11:25 AM UTC

   An automated message was sent earlier from Mendix Support with the title “A message from Mendix Support” to some recipients. Please disregard this message, if you received it as it was sent in error. We apologize for any confusion and appreciate your understanding.

2. resolved Feb 02, 2026, 09:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2026, 09:31 AM UTC· resolved Jan 23, 2026, 04:32 PM UTC

1. investigating Jan 23, 2026, 09:31 AM UTC

   We are investigating an issue affecting deployments. The problem appears to be related to the Autodeploy feature. Until the investigation is complete, please do not create packages using Autodeploy.

2. investigating Jan 23, 2026, 10:58 AM UTC

   We are investigating an issue affecting deployments. The problem appears to be related to the Autodeploy feature. Until the investigation is complete, please do not create packages using Autodeploy. This affects both Mendix on Azure and Mendix on Kubernetes portal

3. identified Jan 23, 2026, 11:31 AM UTC

   We've pinpointed the problem to the Autodeploy feature and deployments made through Studio Pro. We're actively working on a solution! In the meantime, please create your packages via the portal and deploy them manually. For any deployment packages that previously failed, we kindly ask you to create new ones and deploy those instead.

4. identified Jan 23, 2026, 01:11 PM UTC

   We have found the fix and plan on releasing in 10 minutes

5. identified Jan 23, 2026, 01:11 PM UTC

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

6. monitoring Jan 23, 2026, 01:27 PM UTC

   A fix addressing the Autodeploy problem has been released and rolled out. We will monitor the environment to ensure the issue is resolved.

7. resolved Jan 23, 2026, 04:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2026, 01:19 PM UTC· resolved Jan 20, 2026, 02:19 PM UTC

1. investigating Jan 19, 2026, 01:19 PM UTC

   We are investigating an incident with application log ingestion on CloudFoundry. Customers may experience delayed availability of application logs on the Mendix Portal. Live logging is not impacted. This incident will be updated in 1 hour, or as events warrant.

2. identified Jan 19, 2026, 02:28 PM UTC

   We have identified the root cause of the issue, but still working on the fix. It is a compatibility issue with OpenSearch 2.x & logstash plugin. This incident will be updated in 1 hour, or as events warrant.

3. identified Jan 19, 2026, 04:07 PM UTC

   As we have mentioned in the previous update, we did find the root cause of the issue. It is taking longer than expected to implement a fix due to technical challenges. This incident will be updated as events warrant.

4. identified Jan 20, 2026, 08:20 AM UTC

   We are happy to share that we have created a fix for the issue. We are planning to roll the fix out to production within 2 hours. This incident will be updated as events warrant.

5. monitoring Jan 20, 2026, 10:01 AM UTC

   We are happy to share that the fix has been deployed to production. The log ingestion pipeline is recovering, and we are closely monitoring its progress. This incident will be updated as events warrant.

6. resolved Jan 20, 2026, 02:19 PM UTC

   The incident has been resolved. The logs are fully recovered on all affected clusters. If you still experience problems, please reach out to our support team.

Read the full incident report →

Started Jan 14, 2026, 05:33 PM UTC· resolved Jan 15, 2026, 08:50 AM UTC

1. investigating Jan 14, 2026, 05:33 PM UTC

   We are investigating an incident with failing deployments on US-West. Customers may experience failures with new deployments. This incident will be updated in 1 hour, or as events warrant.

2. monitoring Jan 14, 2026, 06:46 PM UTC

   We have implemented a fix and are currently monitoring the cluster. Any previously failed deployments can be tried again.

3. resolved Jan 15, 2026, 08:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 14, 2026, 02:56 PM UTC· resolved Jan 15, 2026, 08:50 AM UTC

1. investigating Jan 14, 2026, 02:56 PM UTC

   We are investigating an incident with failing deployments for Mendix Runtime version 9.24.41. Customers may experience failures with new deployments. This incident will be updated in 1 hour, or as events warrant.

2. resolved Jan 15, 2026, 08:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 24, 2025, 10:59 AM UTC· resolved Dec 24, 2025, 10:59 AM UTC

1. identified Dec 24, 2025, 10:59 AM UTC

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

2. resolved Dec 24, 2025, 10:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 10, 2025, 06:04 AM UTC· resolved Jan 08, 2026, 07:57 AM UTC

1. investigating Dec 10, 2025, 06:04 AM UTC

   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.

2. investigating Dec 10, 2025, 06:05 AM UTC

   We are continuing to investigate this issue.

3. investigating Dec 16, 2025, 02:36 PM UTC

   We are continuing to investigate issue with Webhook Portal's degraded performance

4. investigating Dec 24, 2025, 12:36 PM UTC

   We are continuing to investigate issue with Webhook Portal's degraded performance

5. investigating Dec 30, 2025, 10:42 AM UTC

   We are continuing to investigate this issue.

6. investigating Dec 30, 2025, 11:59 AM UTC

   Webhooks functionality is working as expected now. However, some customers are getting errors while testing the webhook through test Webhook functionality.

7. identified Dec 30, 2025, 12:19 PM UTC

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

8. resolved Jan 08, 2026, 07:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 09, 2025, 06:46 PM UTC· resolved Dec 16, 2025, 02:23 PM UTC

1. investigating Dec 09, 2025, 06:46 PM UTC

   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.

2. monitoring Dec 10, 2025, 02:22 PM UTC

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

3. resolved Dec 16, 2025, 02:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 10:01 AM UTC· resolved Dec 05, 2025, 10:04 AM UTC

1. investigating Dec 05, 2025, 10:01 AM UTC

   We noticed a strange behavior in Academy, only taking an exam is affected. We are currently investigating the issue.

2. resolved Dec 05, 2025, 10:04 AM UTC

   The incident has been identified and resolved.

Read the full incident report →

Started Nov 17, 2025, 09:22 AM UTC· resolved Nov 17, 2025, 11:14 AM UTC

1. investigating Nov 17, 2025, 09:22 AM UTC

   We are currently experiencing reduced performance and increased error rates in Mendix Cloud EU: AWS Frankfurt 2. The teams are working on resolving it.

2. identified Nov 17, 2025, 09:37 AM UTC

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

3. monitoring Nov 17, 2025, 10:00 AM UTC

   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.

4. resolved Nov 17, 2025, 11:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 12:03 PM UTC· resolved Nov 10, 2025, 10:28 AM UTC

1. investigating Nov 07, 2025, 12:03 PM UTC

   For older operator versions(below 2.24.0), we are facing an issue where the Private cloud apps are converting to Trial mode

2. identified Nov 07, 2025, 12:04 PM UTC

   We have identified the fix and currently working on deploying the fix in the Mendix on Kubernetes Portal.

3. identified Nov 07, 2025, 12:06 PM UTC

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

4. monitoring Nov 07, 2025, 12:42 PM UTC

   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.

5. monitoring Nov 10, 2025, 09:57 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Nov 10, 2025, 10:28 AM UTC

   This incident has been resolved.

Read the full incident report →