outages.live
Live

Elastic Cloud

Elastic Cloud is reporting partial outage

Checked 12 s ago Partial outage

Partial System Outage

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

Elastic Cloud reports a connectivity disruption in AWS Bahrain (me-south-1). Elasticsearch, Kibana, APM, snapshot storage, deployment orchestration, and AWS infrastructure health are affected in that region. Elastic Cloud identified the issue and removed the region from new deployment selection on cloud.elastic.co. Existing deployments stay inaccessible.

Partial outageupdated 41 d ago

History

90 days agoToday

Incidents in 90 days

24

Days with an incident

90

Median duration

4 h 48 min

Longest incident

30 days

Components

548

AWS N. Virginia (us-east-1)

AWS EC2 Health: us-east-1 Operational
90 days agoNo incidentsToday
Snapshot Storage Infrastructure (S3): us-east-1 Operational
90 days agoNo incidentsToday
AWS Infrastructure health: us-east-1 Operational
90 days agoNo incidentsToday
Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-1 Operational
90 days agoNo incidentsToday
Elasticsearch connectivity: AWS us-east-1 Operational
90 days agoNo incidentsToday
Kibana connectivity: AWS us-east-1 Operational
90 days agoNo incidentsToday
APM connectivity: AWS us-east-1 Operational
90 days agoNo incidentsToday

AWS São Paulo (sa-east-1)

AWS EC2 Health: sa-east-1 Operational
90 days agoNo incidentsToday
Snapshot Storage Infrastructure (S3): sa-east-1 Operational
90 days agoNo incidentsToday
AWS Infrastructure health: sa-east-1 Operational
90 days agoNo incidentsToday
Deployment orchestration (Create/Edit/Restart/Delete): AWS sa-east-1 Operational
90 days agoNo incidentsToday
Elasticsearch connectivity: AWS sa-east-1 Operational
90 days agoNo incidentsToday
Kibana connectivity: AWS sa-east-1 Operational
90 days agoNo incidentsToday
APM connectivity: AWS sa-east-1 Operational
90 days agoNo incidentsToday

AWS N. California (us-west-1)

AWS EC2 Health: us-west-1 Operational
90 days agoNo incidentsToday
Snapshot Storage Infrastructure (S3): us-west-1 Operational
90 days agoNo incidentsToday
AWS Infrastructure health: us-west-1 Operational
90 days agoNo incidentsToday
Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-1 Operational
90 days agoNo incidentsToday
Elasticsearch connectivity: AWS us-west-1 Operational
90 days agoNo incidentsToday
Kibana connectivity: AWS us-west-1 Operational
90 days agoNo incidentsToday
APM connectivity: AWS us-west-1 Operational
90 days agoNo incidentsToday

AWS Ireland (eu-west-1)

AWS EC2 Health: eu-west-1 Operational
90 days agoNo incidentsToday
Snapshot Storage Infrastructure (S3): eu-west-1 Operational
90 days agoNo incidentsToday
Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration2 h 29 min04:04 to 06:33Elastic Support Portal is unavailablePartial outage

The upstream provider has completed its fix, and access to the Elastic Support portal has been restored. Customers can authenticate to the support portal again. We are considering this issue resolved and will be providing no further updates. If you continue to have issues, please contact us.

Oct 22, 2026

Duration9 h 31 min11:19 to 20:50403 error when trying to access Autoops in newly created serverless projectsPartial outage

We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.

Oct 20, 2026

Duration6 h 57 min20:07 to 03:05Elastic Cloud scaling issues in AzurePartial outage

Engineers have mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. Scaling is working as expected.

Duration15 h 3 min06:51 to 21:54Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)Partial outage

The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone. Elastic Cloud Hosted: Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Some deployments may still be unavailable or degraded, and may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support.

Oct 8, 2026

Duration8 h 12 min16:42 to 00:54Delayed or Unavailable project operation in GCP us-central1Partial outage

The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.

Oct 6, 2026

Duration3 h 50 min14:04 to 17:54Delayed Serverless Metrics in Azure UAE North regionPartial outage

The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.

Sep 23, 2026

Duration1 h 59 min14:04 to 16:03Degraded Performance: Cloud Provisioning DelaysPartial outage

This issue has been resolved.

Sep 17, 2026

Duration41 min15:50 to 16:31AutoOps node metrics temporarily unavailable in some regionsPartial outage

The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.

Sep 16, 2026

Duration2 h 21 min13:17 to 15:38Elastic Support Portal unavailablePartial outage

The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.

Sep 12, 2026

Duration8 h 24 min23:21 to 07:45Delayed Metrics in Cloud Console - GCP us-east4Partial outage

The metrics ingestion delay in GCP us-east4 has been fully resolved. All queued data has been processed and metrics are now showing in the console in real time.

Sep 10, 2026

Duration21 h01:30 to 22:31Kibana access restored for UI-assigned Organization Owners on Hosted deploymentsPartial outage

This incident has been resolved.

Sep 9, 2026

Duration8 days20:44 to 10:30Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputPartial outage

We have confirmed that Elastic Agents are no longer experiencing enrollment failures related to this issue. Corrected Fleet Server releases (9.5.4 / 9.4.6) have been available on Elastic Cloud Hosted and Elastic Cloud Enterprise stack packs since September 10, 2026, and all known affected deployments have confirmed recovery. If you upgraded to an affected release before that time and have not yet applied the mitigation, guidance is available here: https://support.elastic.co/knowledge/bee1c75c.

Sep 2, 2026

Duration1 min00:04 to 00:04Elevated Error Rates for Specific Models Impacting Elastic Inference Service in EU RegionsPartial outage

From 21:50 to 23:42 UTC, we encountered elevated error rates for Anthropic Claude Haiku 4.5, OpenAI GPT-5.6, and Google Gemini 2.5 Flash with the Elastic Inference Service in EU regions. This issue has now been resolved.

Affected components

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

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.live/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.live/feed.xml?providers=elastic
Slack
/feed subscribe https://outages.live/feed.xml?providers=elastic

Go from tracking outages to fixing production issues with Polylane.

Try Polylane