Live / Incidents / Elastic Cloud (Public)

Elastic Cloud (Public): Connectivity disruption for AWS Bahrain (me-south-1)

Elastic Cloud (Public) · elastic.coImpact: majoridentified2026-09-21 15:21 UTC

Public — what happened

Summary

Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].

Timeline

Started — 2026-03-02 06:23 UTC
Last update — 2026-09-21 15:21 UTC
Ongoing at last check.

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see

Customers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Elastic Cloud (Public) report →

Related: Elastic Cloud (Public) status & history. SquidGrid is not affiliated with Elastic Cloud (Public).