Is Elastic Cloud Down?

This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident. --- [2026-08-20T21:59:24.406Z] (identified) We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline. Based on our investigation, customer workloads were not affected. --- [2026-08-20T20:53:17.915Z] (investigating) We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. We will provide an update within 1 hour. --- [2026-08-20T20:22:56.111Z] (investigating) We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. Our team is actively investigating the root cause. We will provide an update within 30 minutes.

Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected. --- [2026-08-20T14:05:15.437Z] (monitoring) We have determined that the issue stems from an upstream problem with Azure's storage component. Upon examination, the impact is limited strictly to new project initialization times, resulting in longer creation times for Serverless projects in the Azure eastus region. We will provide a further update once the issue has been resolved. --- [2026-08-20T12:48:02.384Z] (investigating) An issue affecting the creation of new Serverless projects in Azure's eastus region has been identified. Our team is actively investigating to determine the root cause. We will provide a follow-up status update within the next hour or as soon as the root cause is established, whichever occurs first.

Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue resolved and will be providing no further updates. --- [2026-08-14T09:22:04.044Z] (identified) Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-value terms queries utilize a different Lucene query type that was not covered by that fix. Time Series Data Streams (TSDB) and columnar indices/data streams remain affected for this query pattern, as indexing is disabled by default on those fields. Affected terms queries may return false-positive matches (including documents that should have been excluded) and report higher document counts than expected. No error is raised, so queries will appear to complete successfully. What you can do: - If you have not yet upgraded to 9.5.*, we recommend deferring the upgrade until version 9.5.2 is available. - If you are already running 9.5.*, contact Elastic Support if you need help determining whether your searches are affected. We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update when the fix is ready.