Elastic Cloud Outage History

Elastic Cloud experienced a major issue preventing users from creating new Serverless projects in the AWS ap-southeast-2 region. The problem affected project creation functionality for users in that specific region. The engineering team investigated and resolved the issue within 36 minutes.

A disruption in metric data ingestion caused missing metrics visualizations in the Elastic Cloud console for deployments in the Azure North Europe region, preventing users from viewing recent metric data in charts and monitoring views. The incident lasted 47 minutes, during which the problem was identified and stabilized before full system recovery. Functionality returned to normal after the system recovered completely.

New Elastic Cloud customers and trial users were unable to access the AutoOps dashboard across all regions for approximately 7 days, while existing customers remained unaffected. The issue was initially mitigated by restarting a backend service, followed by implementation of a permanent resolution. The incident was fully resolved after monitoring confirmed the fix remained stable.

Elastic Cloud experienced a major outage affecting multiple Serverless projects from 08:00 UTC to 09:40 UTC on May 11, causing Search, Ingest, and EIS functionality to become unavailable for 3.2 hours. The root cause was identified and resolved, with the service returning to normal operation and no further impact expected.

Elastic Cloud experienced a major incident where some customers faced issues with email alerts for 6.9 hours. The service disruption affected email alert delivery functionality across the platform. The issue was resolved after implementing a solution that restored email delivery, with monitoring confirming successful operation before full resolution.

Elastic Cloud experienced delayed AutoOps metrics for customers in the AWS us-east-1 region due to an identified system issue. The problem affected metric delivery and monitoring capabilities for users in that specific region. The issue was resolved after 52 minutes of mitigation efforts.

A disruption in metric data ingestion affected Elastic Cloud deployments in the us-east-1 region, causing missing metrics visualizations in the Cloud console and preventing recent metric data from appearing in charts or monitoring views. The incident lasted 3.9 hours, with the system showing gradual signs of stabilization before full recovery was achieved.

Elastic Cloud experienced connectivity issues in the AWS EU West 3 (Paris) region for 53 minutes, causing elevated error rates and latency for a subset of customers. The incident was caused by an underlying cloud infrastructure provider issue that affected the region's ingress layer traffic. The problem was resolved through remediation with the cloud provider, with traffic returning to normal levels and all monitoring alerts clearing.

Elastic Cloud experienced elevated 5xx error rates for the Google Gemini Embedding v1 model (.google-gemini-embedding-001) in their Elastic Inference Service (EIS) for 4.1 hours. The errors originated from Google's provider API, and the incident was escalated to Google for resolution. The upstream service provider issue was resolved, restoring normal access to the embedding model.

A recent change to Elastic Cloud's Privatelink implementation caused the deployment API to report incorrect URLs, resulting in connectivity issues for customers relying on those URLs. The incident lasted 23.2 hours and affected customers' ability to connect to their deployments through Privatelink. The issue was resolved by deploying a fix to the User Console that corrected the hostname reporting.