Mendix Technology B.V. Status

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.

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.

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.

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

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.

We will update the incident as events warrant.

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.

As mentioned in our previous message, environments using a premium resource pack are not affected.

We will update the incident as events warrant.

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.

We will update the incident as events warrant.

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

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

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

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.