Incident in Middle East (Bahrain) Region

Update timeline

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.