Connectivity disruption for AWS Bahrain (me-south-1)

Update timeline

1. identified Mar 02, 2026, 06:23 AM UTC

   We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.

2. identified Mar 09, 2026, 03:01 PM UTC

   This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

3. identified Mar 16, 2026, 07:46 PM UTC

   This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

4. identified Mar 23, 2026, 04:20 PM UTC

   There are no new updates. This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

5. identified Mar 24, 2026, 09:29 AM UTC

   We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.

6. identified Mar 24, 2026, 11:09 AM UTC

   This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

7. identified Apr 02, 2026, 12:00 AM UTC

   As this incident remains ongoing with no recovery timeline provided by AWS, we have removed AWS Bahrain (me-south-1) from the available region selection on cloud.elastic.co. The region is currently unavailable for the creation of new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS connectivity disruption. Customers in this region should continue to work through Elastic support channels. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].

8. identified Apr 20, 2026, 05:46 PM UTC

   Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unavailable for the foreseeable future. We continue to support impacted customers individually through our support channels. If you have not yet done so, please open a case so we can assist with your recovery options. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:[email protected]. Apr 20, 2026 — 00:00 UTC