Incident in Middle East (Bahrain) Region
Incident Lifecycle
Incident Timeline
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.
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.
Mar 27, 2026 at 9:35 AM 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: We will only update again if there is actually an update. Subscribe to get updates automatically.
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.
Mar 20, 2026 at 2:52 PM 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 20th 2026
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
Mar 17, 2026 at 9:48 AM 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: Monday March 16th 2026, 15:00 UTC
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
Mar 13, 2026 at 3:28 PM 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
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
Mar 10, 2026 at 3:23 PM 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.
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.
Mar 9, 2026 at 9:15 AM 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.
As mentioned in our previous message, environments using a premium resource pack are not affected.
We will update the incident as events warrant.
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.
Mar 4, 2026 at 2:30 PM 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.
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.
Mar 3, 2026 at 3:53 PM UTC
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.
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.
Mar 2, 2026 at 3:39 PM UTC
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.
Customers using the premium plan will not be affected.
We will update the incident as events warrant.
Mar 2, 2026 at 8:21 AM UTC
Investigating
We are experiencing some difficulties reaching the Middle East (Bahrain) region.
Mar 2, 2026 at 5:48 AM UTC
Was your business affected by this Mendix Technology outage?
Set up instant alerts for Mendix Technology — be the first to know about outages via email, Slack, Teams, or Discord.