Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): Connectivity disruption for AWS Bahrain (me-south-1)
Elastic Cloud (Public) · elastic.coMajor incidentidentified2026-09-21 15:21 UTC
Public — what happened
Summary
Elastic Cloud reported a major disruption starting 2026-03-02 at 06:23 UTC affecting its services in the AWS Bahrain (me-south-1) region, which it attributed to localized power and connectivity problems at AWS. On 2026-03-24 the company flagged a further possible disruption in the same region, and by 2026-04-02 it had pulled the region from the options for new deployments, saying existing deployments there could not be reached. Through its latest update on 2026-09-21, Elastic Cloud said the issue was still unresolved, that AWS had given no recovery timeline, and that customers should treat the region as unavailable for the foreseeable future and contact Elastic support for help.
Affected
AWS EC2 Health: me-south-1, Snapshot Storage Infrastructure (S3): me-south-1, Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1, APM connectivity: AWS me-south-1, AWS Infrastructure health: me-south-1, Elasticsearch connectivity: AWS me-south-1, Kibana connectivity: AWS me-south-1
Timeline
- Started — 2026-03-02 06:23 UTC
- Identified — 2026-03-02 06:23 UTC (15 updates)
- Ongoing at last check.
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 seeCustomers 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 →
More from Elastic Cloud (Public)