Elastic Cloud Outage History

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.

Elastic Cloud experienced a major 20.3-hour incident where users could not connect to Kibana through the Cloud UI via SAML SSO, specifically affecting PrivateLink customers while other hosted deployments remained unaffected. The engineering team identified the root cause, deployed a fix, and confirmed full resolution with no further customer impact.

The Elastic Cloud Synthetics service in the us-east-4 region experienced a major incident where customer monitor jobs failed to run on their expected schedules. The issue affected monitoring capabilities for customers using the Synthetics service in that region for approximately 2.8 hours. The problem was identified and resolved, restoring normal scheduling functionality for all affected monitor jobs.

Elastic Cloud experienced elevated 5xx error rates affecting Claude Sonnet 4.5 model inference endpoints, including chat completion and completion endpoints for both Anthropic Claude 4.5 Sonnet and GP-LLM-v2 models. The incident lasted 1.2 hours before all endpoints returned to normal operation.

Elastic Cloud experienced a major AutoOps outage in the AWS us-east-1 region lasting 2.9 hours, causing customer deployments to be incorrectly marked as inactive and preventing access to recent metrics. The engineering team identified the root cause, applied mitigations, and restored full AutoOps functionality. The incident was fully resolved after a monitoring period to ensure system stability.