Elastic Cloud 장애 기록

1. 2026년 9월 10일 AM 1:30 UTCidentified

   We have identified and are in the process of fixing+mitigating a bug in our permissions management UI that is prevents users with the Organisation Owner role and Cloud Console, Elasticsearch, and Kibana access from accessing Kibana in Hosted Deployments.

2. 2026년 9월 10일 AM 6:03 UTCidentified

   Update: This incident is still ongoing and we are continuing to investigate.

3. 2026년 9월 10일 AM 9:51 UTCmonitoring

   Update: The fix has been deployed to production and we have applied a data correction to affected accounts, restoring Kibana access for impacted users. We are monitoring to confirm full resolution.

1. 2026년 9월 9일 PM 8:44 UTCidentified

   We've identified a bug in Fleet Server 9.5.3 (also present in 9.4.6) that can cause Elastic Agents to crash-loop and go offline when Fleet pushes a configuration update, including enrollment, a policy change, or a routine revision bump. This only affects policies that use Fleet's remote Elasticsearch output feature. Recommendation: If you use Fleet's remote Elasticsearch output, do not upgrade to 9.5.3 or 9.4.6 until a fixed version is available. If you're already on an affected version and experiencing agent check-in failures, contact Support for remediation steps. A fix has been merged and will ship in the next 9.5.x and 9.4.x releases. Known Issue documentation: fleet-server#7791, elastic-agent#16542.

1. 2026년 9월 2일 AM 12:04 UTCresolved

   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.

1. 2026년 9월 1일 PM 3:18 UTCinvestigating

   We are currently investigating an issue impacting services running in GCP us-central1.  We will provide additional updates as we learn more about the scope of impact.

2. 2026년 9월 1일 PM 3:51 UTCidentified

   An ongoing issue is impacting services running in GCP us-central1.  This includes, but is not limited to Elastic Cloud Hosted and Serverless projects in the region and our Docker Registry service.  We are continuing to monitor the situation and will provide updates when they are available.

3. 2026년 9월 1일 PM 4:15 UTCidentified

   An ongoing upstream CSP issue is impacting services running in GCP us-central1. This includes, but is not limited to Elastic Cloud Hosted and Serverless projects in the region and our Docker Registry service. We are continuing to monitor the situation and will provide updates when they are available.

4. 2026년 9월 1일 PM 4:22 UTCmonitoring

   We are seeing signs of recovery for services in GCP us-central1 impacted by an upstream CSP issue .  We are continuing to monitor the situation and will provide updates as they become available.

5. 2026년 9월 1일 PM 8:05 UTCresolved

   This issue has been resolved.

1. 2026년 9월 1일 AM 8:16 UTCinvestigating

   We are aware of a bug affecting customers on Elasticsearch versions 9.5.0, 9.5.1 and 9.5.2 where bulk index operations processed on the primary shard can result in divergence on the replicas resulting in high disk usage and long-running recoveries. The team is working on a fix. More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues The next update will be in the next 2 hours or sooner if needed.

2. 2026년 9월 1일 AM 11:07 UTCidentified

   We have identified the root cause and the team is working on a fix scheduled to be released in Elasticsearch version 9.5.3 What you can do: - If you have not yet upgraded to 9.5.*, you are not affected as upgrades to 9.5 have been disabled until 9.5.3 is released - If you are already running 9.5 and experience the symptoms of this issue, please contact Elastic Support. More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues

3. 2026년 9월 1일 PM 3:46 UTCidentified

   The fix has been identified and backported to the Elasticsearch 9.5 patch branch. The teams are performing the needed validations before scheduling and rolling out the 9.5.3 release.

4. 2026년 9월 3일 PM 12:13 UTCmonitoring

   Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible.

5. 2026년 9월 3일 PM 3:47 UTCmonitoring

   Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible. Impacted customers are advised to follow the workaround steps from https://github.com/elastic/elasticsearch/issues/158212 after the upgrade.

1. 2026년 8월 27일 PM 5:11 UTCmonitoring

   On August 26, at around 00:00 UTC we deployed a change in Managed Inputs that affected some rules in our internal DNS provider, removing the .apm endpoints some of our Serverless customers. The service was restored around 9AM UTC on the same day. During this time, some customers would have experienced unavailability of the .apm endpoint, for a period in the 9 hour window. We are putting some checks and alerts in place to ensure this does not happen again.

2. 2026년 8월 27일 PM 6:33 UTCresolved

   This is now resolved

1. 2026년 8월 20일 PM 8:22 UTCinvestigating

   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.

2. 2026년 8월 20일 PM 8:53 UTCinvestigating

   We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. We will provide an update within 1 hour.

3. 2026년 8월 20일 PM 9:59 UTCidentified

   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.

4. 2026년 8월 20일 PM 10:13 UTCresolved

   This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.

1. 2026년 8월 20일 PM 12:48 UTCinvestigating

   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.

2. 2026년 8월 20일 PM 2:05 UTCmonitoring

   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.

3. 2026년 8월 20일 PM 4:22 UTCresolved

   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.

1. 2026년 8월 14일 AM 9:22 UTCidentified

   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.

2. 2026년 8월 20일 PM 5:09 UTCresolved

   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.

1. 2026년 8월 13일 AM 8:32 UTCinvestigating

   We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating

2. 2026년 8월 13일 PM 2:45 UTCinvestigating

   We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.

3. 2026년 8월 13일 PM 6:26 UTCmonitoring

   Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.

4. 2026년 8월 17일 AM 11:40 UTCresolved

   The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference

1. 2026년 8월 13일 AM 3:57 UTCinvestigating

   We are investigating failures with Serverless project creation.

2. 2026년 8월 13일 AM 5:28 UTCinvestigating

   We're currently investigating an issue affecting Serverless project creation and modifications. You may experience delays or failures when creating new projects or updating existing project settings. What's affected: - Creating new Serverless projects - Modifying project settings in the Cloud UI or over the API What's not affected: - Running Serverless projects continue to operate normally - Existing project workloads are unimpacted We'll provide an update within 2 hours, or sooner if the situation changes.

3. 2026년 8월 13일 AM 6:04 UTCmonitoring

   We've identified and resolved the issue affecting Serverless project creation and modifications. Our fix has been deployed, and all services are operating normally. Current status: - Creating and modifying Serverless projects is fully operational - All systems are performing as expected We're continuing to monitor closely for any recurrence.

4. 2026년 8월 13일 AM 8:40 UTCresolved

   We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.

1. 2026년 8월 6일 PM 5:41 UTCresolved

   On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.

1. 2026년 8월 5일 PM 10:59 UTCidentified

   Elasticsearch 9.5.0 contains a defect that can cause searches to return incorrect results for any index or data stream that disables indexing on a queried field . A query that excludes values using a must_not clause may fail to exclude them when the targeted field has doc values enabled but is not indexed for search. Affected searches can return documents that should have been excluded and report higher document counts than expected, and results may vary between runs of the same query. No error is raised, so affected queries appear to succeed. Dashboards, alerting rules, and anything else built on these searches may report inaccurate values. Both the query DSL and ES|QL are affected. Time series (TSDB) data streams are the most likely to be affected, because indexing is disabled by default for these fields. Columnar indices, currently in technical preview, are affected for the same reason. Any index or data stream that disables indexing on a queried field can be affected. This affects Elasticsearch 9.5.0 on Elastic Cloud Hosted, Elastic Cloud Enterprise, and self-managed deployments, as well as Elasticsearch Serverless projects. Elasticsearch 9.4.x and earlier are not affected. There is no impact to cluster availability, connectivity, or data ingestion. What you can do: - If you have not yet upgraded to 9.5.0, we recommend deferring the upgrade until a fixed version is available. - If you are already running 9.5.0, 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 by 10:00 UTC August 6.

2. 2026년 8월 5일 PM 11:18 UTCidentified

   Further investigation confirmed the impact of this issue was limited to boolean queries containing a must, filter, or should clause, along with a must_not clause on unindexed fields. Such queries can return false-positives returning documents that should have been excluded and report higher document counts than expected. We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update by 10:00 UTC August 6.

3. 2026년 8월 6일 PM 12:12 UTCidentified

   A patch release containing the fix is in progress and it is expected to be available within the next week. Our recommendation to defer upgrading to 9.5.0 until 9.5.1 is available remains unchanged.

4. 2026년 8월 12일 AM 8:59 UTCresolved

   Elasticsearch 9.5.1 has been released and contains the fix for this issue. Customers running 9.5.0 should upgrade to 9.5.1. At this time we are considering this issue resolved and will be providing no further updates.

1. 2026년 7월 21일 PM 2:24 UTCinvestigating

   우리는 고객의 하위 세트에 영향을 미치는 Hosted Deployments에 대한 Instance Capacity의 계량과 문제가 발견되었습니다. 우리는 현재 고객의 작은 숫자로 제한 될 수있는 영향을 믿지만 여전히이 문제의 모든 발생을 확인하고 수정하기 위해 노력하고 있습니다. 우리는 필요한 청구 보정을 유발합니다.

2. 2026년 7월 21일 PM 11:15 UTCinvestigating

   우리는 여전히 고객의 작은 숫자에 영향을 미치는 미터화 문제점을 조사하고 있습니다. 우리는 필요한 청구 보정을 유발합니다. 새로운 정보를 사용할 때 또 다른 업데이트가 제공됩니다.

3. 2026년 7월 22일 AM 10:49 UTCinvestigating

   우리는 여전히 고객의 작은 숫자에 영향을 미치는 미터화 문제점을 조사하고 있습니다. 새로운 정보를 사용할 때 추가 업데이트를 제공합니다.

4. 2026년 7월 22일 PM 11:14 UTCresolved

   모든 계량 오류가 수정되었습니다. 우리는 영향을받는 고객의 작은 숫자로 환불을 발급합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 PM 1:45 UTCidentified

   RESOLVED - 7 월 18 02 : 40 UTC 및 7 월 20 : 14 : 00 UTC 사이에 탄성 에이전트의 하위 세트는 모든 지역에서 AutoOps에 메트릭을보고 할 수 없습니다. 아래 문제점은 정확하고 자료는 일반적으로 흐릅니다. 충격적인 배치는 이 시간 동안 AutoOps 감시 자료에 있는 몇몇 간격을 주의할지도 모릅니다. 이 사건을 이미 해결하고, 복부적으로 게시됩니다.

2. 2026년 7월 21일 PM 2:21 UTCresolved

   이 사건은 7월 20일 14:00 UTC에 해결되었으며, 개조되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 AM 9:36 UTCinvestigating

   우리는 현재 Gmail 계정과 Elastic Cloud 사용자에 대한 이메일을 통해 멀티 요인 인증 (MFA)에 영향을 미치는 문제점을 조사하고 있습니다. 수정된 사용자는 이메일 MFA 코드를 수신할 때 긴 지연 또는 실패를 경험할 수 있습니다. 유효한 운동: - 등록된 경우 MFA Factor(Authenticator App / TOTP 또는 WebAuthn)을 사용하십시오. - "Log in with Google" 소셜 로그인 버튼을 사용하여 인증. 참고: 프로젝트 및 배포에 대한 API 키 액세스는 완전히 운영됩니다. 우리는이 문제를 해결하기 위해 파트너와 협력하고 우리가 할 수있는 한 빨리 업데이트를 제공 할 것입니다.

2. 2026년 7월 21일 AM 10:56 UTCinvestigating

   업데이트: 이 사건은 여전히 진행되고 우리는 조사를 계속하고 있습니다. 우리는 현재 Gmail 계정과 Elastic Cloud 사용자에 대한 이메일을 통해 멀티 요인 인증 (MFA)에 영향을 미치는 문제점을 조사하고 있습니다. 수정된 사용자는 이메일 MFA 코드를 수신할 때 긴 지연 또는 실패를 경험할 수 있습니다. 유효한 운동: - 등록된 경우 MFA Factor(Authenticator App / TOTP 또는 WebAuthn)을 사용하십시오. - "Log in with Google" 소셜 로그인 버튼을 사용하여 인증. 참고: 프로젝트 및 배포에 대한 API 키 액세스는 완전히 운영됩니다. 우리는이 문제를 해결하기 위해 파트너와 협력하고 우리가 할 수있는 한 빨리 업데이트를 제공 할 것입니다.

3. 2026년 7월 21일 PM 2:25 UTCinvestigating

   업데이트: 이 사건은 여전히 진행되고 우리는 조사를 계속하고 있습니다.

4. 2026년 7월 21일 PM 11:10 UTCmonitoring

   납품 지연은 mitigated. 우리는 납품을 지키는 것을 계속할 것입니다 안정되어 있습니다.

5. 2026년 7월 23일 PM 4:37 UTCresolved

   납품 지연은 해결되었습니다, MFA 이메일 납품은 모든 고객을 위한 완전히 기능입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 PM 12:10 UTCresolved

   해결 – 이 사건은 해결됩니다. 7월 18 02:40 UTC와 7월 20 14:00 UTC 사이, Elastic Agents의 하위 세트는 모든 지역에서 AutoOps에 메트릭을보고 할 수 없었다. 아래 문제점은 정확하고 자료는 일반적으로 흐릅니다. 충격적인 배치는 이 시간 동안 AutoOps 감시 자료에 있는 몇몇 간격을 주의할지도 모릅니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 15일 AM 12:15 UTCinvestigating

   우리는 클라우드 콘솔과의 투자 오류가 생성, 업데이트, 삭제 및보기 Elastic Cloud Hosted 배포에 영향을 미치는 영향. 우리의 팀은 활발하게 그 원인을 조사하고 서비스를 복원 할 수 있도록.

2. 2026년 7월 15일 AM 12:31 UTCmonitoring

   Cloud Console을 통해 Elastic Cloud Hosted 배포를 관리하는 기능은 복원되었습니다

3. 2026년 7월 15일 AM 1:12 UTCresolved

   이 사건은 해결되었습니다

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 13일 PM 12:15 UTCinvestigating

   Microsoft 로그인 자격 증명을 사용하여 Elastic Cloud에 대해 인증하는 문제를 조사하고 있습니다

2. 2026년 7월 13일 PM 12:19 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 2일 AM 12:54 UTCinvestigating

   EIS의 영향을 받은 고객에 대한 지속적인 영향을 주었습니다. 우리의 팀은 이전 구제 문제를 조사하고 모든 영향을받는 환경을 완전히 복원하기 위해 노력하고 있습니다.

2. 2026년 7월 2일 AM 2:24 UTCmonitoring

   EMEA 지역의 EIS와 함께 고객의 하위 세트에 영향을 미치는 문제는 미묘하고 서비스가 복원되었습니다.

3. 2026년 7월 2일 AM 3:00 UTCresolved

   EMEA 지역의 EIS와 함께 고객의 하위 세트에 영향을 미치는 사건은 해결되었습니다. 서비스는 완전히 회복되고 팀은 안정성을 확인했습니다.

공식 인시던트 업데이트를 자동 번역했습니다.