Mendix Technology B.V. Status

Resolved: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Investigating: 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.

Resolved: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Investigating: 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.

Resolved: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Investigating: 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.

Resolved: This incident has been resolved.

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

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

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

Identified: 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.

Investigating: 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

Investigating: 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.

Resolved: This incident has been resolved.

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

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

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

Identified: 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.

Investigating: 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

Investigating: 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.