outages.live
Live
Elastic CloudIncident · 2026-03-02 06:23 UTC

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

Partial outageOfficial update
0

Elastic Cloud reports connectivity problems in AWS Bahrain (me-south-1). The affected components include Elasticsearch, Kibana, APM, snapshot storage, deployment orchestration, and AWS infrastructure health. Elastic Cloud has identified the issue and states that the region is unavailable for the foreseeable future.

A language model wrote this summary from the updates of Elastic Cloud.

State

Identified

Started

244 d ago

2026-03-02 06:23 UTC

Ongoing for

244 days

Worst impact

Partial outage

Timeline

1 update
Mar 2May 2Jul 2Sep 1Nov 1
Partial outageUpdate postedDates in UTC

Identified

244 days 100%

Updates

Times in UTC

As posted by Elastic Cloud

Identified2026-10-31 21:45 UTC

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 support@elastic.co.

Affected components

14
AWS EC2 Health: me-south-1Snapshot Storage Infrastructure (S3): me-south-1Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1APM connectivity: AWS me-south-1AWS Infrastructure health: me-south-1Elasticsearch connectivity: AWS me-south-1Kibana connectivity: AWS me-south-1AWS Bahrain (me-south-1) - AWS EC2 Health: me-south-1

Elastic Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

90

Median duration

Not enough data

This incident

Not comparable

Follow Elastic Cloud

Your coding agent knows when Elastic Cloud is down, and tells you when a failure is theirs, not yours. You can also get Elastic Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "elastic" and tell me if Elastic Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=elastic
Slack
/feed subscribe https://outages.cc/feed.xml?providers=elastic

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane