Mendix incident

Incident in Middle East (UAE) region

Critical Resolved View vendor source →

Mendix experienced a critical incident on March 1, 2026 affecting Mendix Cloud Middle East (UAE), lasting 79d 16h. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2026, 04:06 PM UTC
Resolved
May 20, 2026, 08:53 AM UTC
Duration
79d 16h
Detected by Pingoru
Mar 01, 2026, 04:06 PM UTC

Affected components

Mendix Cloud Middle East (UAE)

Update timeline

  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.