Elastic Cloud

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-20 20:07 UTC

   We are investigating an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. New project and deployment creation in Azure may be delayed.

2. identified 2026-10-20 21:24 UTC

   We have identified an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. New project and deployment creation in Azure may be delayed. Engineers are actively working to mitigate the issue.

3. monitoring 2026-10-20 22:27 UTC

   Engineers have identified and mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. We are monitoring the issue to ensure operations continue normally.

4. resolved 2026-10-21 03:05 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:51 UTC

   We are investigating an issue affecting one availability zone in the GCP europe-west2 (London) region. Starting at approximately 06:15 UTC, some Elastic Cloud Hosted and Serverless deployments with capacity in this zone may experience degraded availability or connectivity....

2. identified 2026-10-20 07:56 UTC

   Our cloud provider has confirmed an infrastructure incident affecting a single availability zone (europe-west2-b) in the GCP europe-west2 (London) region, causing network connectivity loss and resource unavailability in that zone. Elastic Cloud Hosted deployments and Elastic...

3. identified 2026-10-20 09:15 UTC

   The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. Elastic Cloud Hosted: Most deployments with resources in the affected zone remain unavailable or degraded. We are seeing early,...

4. identified 2026-10-20 10:32 UTC

   The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. Elastic Cloud Hosted deployments and Elastic Serverless projects with resources in the affected zone may remain unavailable or...

5. identified 2026-10-20 12:24 UTC

   The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is ongoing. We are seeing slight signs of recovery, both from our cloud provider and from our own mitigation work. Elastic Cloud Hosted: Some of...

6. identified 2026-10-20 14:15 UTC

   The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region is recovering. Our cloud provider reports recovery of services for most workloads in the region, and we are seeing progress on our side as the...

7. identified 2026-10-20 17:27 UTC

   The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. We are continuing to work towards full recovery of our services. Elastic Cloud Hosted: An increasing number of affected...

8. resolved 2026-10-20 21:54 UTC

   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...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: GCP Infrastructure health: us-central1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations..

1. investigating 2026-10-08 16:42 UTC

   We are investigating an issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operation.

2. identified 2026-10-08 17:21 UTC

   We have identified an issue with cloud storage affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operations. The provider is investigating the issue, and we are monitoring recovery. We will...

3. identified 2026-10-08 19:17 UTC

   Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations. The provider is continuing to investigate the issue. We are monitoring the situation and will provide another update when more information is...

4. monitoring 2026-10-08 20:47 UTC

   We have observed improvements after mitigations were applied by our upstream cloud storage provider. Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations while recovery continues. We are monitoring...

5. resolved 2026-10-09 00:54 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Azure Infrastructure Health

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-06 14:04 UTC

   Customers with Serverless projects in the Azure UAE North region may see delays in metrics displayed in Cloud UI. The team is investigating the issue and we will post an update in 2 hours or sooner if necessary

2. resolved 2026-10-06 17:54 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-23 14:04 UTC

   We are currently experiencing delays in provisioning new cloud resources due to slowness with an external container image provider. This may result in delays when creating new deployments, scaling existing ones, or relocating instances affected by infrastructure maintenance. As...

2. resolved 2026-09-23 16:03 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 15:50 UTC

   We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data...

2. identified 2026-09-17 16:13 UTC

   We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred. A fix has been validated in one region and is now being rolled out...

3. resolved 2026-09-17 16:31 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-16 13:17 UTC

   We are currently aware that some customers may be unable to access the Elastic Support Portal at this time. We are working with our provider to investigate. If you need to contact support in the meantime, please contact support@elastic.co.

2. monitoring 2026-09-16 14:49 UTC

   We are seeing signs of recovery on the Elastic Support Portal, and customers should now be able to access as normal. We will continue monitoring for 30 minutes before marking this incident as resolved.

3. resolved 2026-09-16 15:38 UTC

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

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-09-12 23:21 UTC

   We are investigating metrics delays in the console.

2. identified 2026-09-13 00:18 UTC

   We've identified and fixed the cause of the metrics delay. The queue is being processed and delayed metrics will be viewable when complete.

3. monitoring 2026-09-13 02:55 UTC

   Metrics queues are being processed and delayed data is starting to show again. We'll monitor to be sure everything catches up as expected.

4. resolved 2026-09-13 07:45 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-10 01:30 UTC

   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. identified 2026-09-10 06:03 UTC

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

3. monitoring 2026-09-10 09:51 UTC

   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.

4. resolved 2026-09-10 22:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-09 20:44 UTC

   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...

2. identified 2026-09-11 14:25 UTC

   We have patched Fleet Server versions 9.5.3 and 9.4.6 with corrected releases deployed as of September 10, 2026 at 21:20 UTC. - Upgrading to the current 9.4.6 or 9.5.3 releases will not be affected by this bug as the updated release contains the fix. - If you upgraded to 9.4.6...

3. identified 2026-09-11 16:00 UTC

   We have patched Fleet Server versions 9.5.3 and 9.4.6 with corrected releases deployed as of September 10, 2026 at 21:20 UTC. - Upgrading to the current 9.4.6 or 9.5.3 releases will not be affected by this bug as the updated release contains the fix. - If you upgraded to 9.4.6...

4. resolved 2026-09-17 10:30 UTC

   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...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude), OpenAI.

Started during Anthropic (Claude): Delays in credit purchases.

1. resolved 2026-09-02 00:04 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: GCP Infrastructure Health, GCP Infrastructure health: us-central1, Elastic Docker Registry

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 15:18 UTC

   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. identified 2026-09-01 15:51 UTC

   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...

3. identified 2026-09-01 16:15 UTC

   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...

4. monitoring 2026-09-01 16:22 UTC

   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. resolved 2026-09-01 20:05 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elastic Cloud Hosted

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-01 08:16 UTC

   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....

2. identified 2026-09-01 11:07 UTC

   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...

3. identified 2026-09-01 15:46 UTC

   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. monitoring 2026-09-03 12:13 UTC

   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. monitoring 2026-09-03 15:47 UTC

   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...

6. resolved 2026-09-30 20:44 UTC

   This issue was resolved in the 9.5.3 release of Elasticsearch. Customers running versions 9.5.0, 9.5.1, or 9.5.2 of Elasticsearch are advised to update to a newer version as soon as possible.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-27 17:11 UTC

   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...

2. resolved 2026-08-27 18:33 UTC

   This is now resolved

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 20:22 UTC

   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. investigating 2026-08-20 20:53 UTC

   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. identified 2026-08-20 21:59 UTC

   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. resolved 2026-08-20 22:13 UTC

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

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elastic Cloud Serverless

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-20 12:48 UTC

   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,...

2. monitoring 2026-08-20 14:05 UTC

   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...

3. resolved 2026-08-20 16:22 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-14 09:22 UTC

   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...

2. resolved 2026-08-20 17:09 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-13 08:32 UTC

   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. investigating 2026-08-13 14:45 UTC

   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. monitoring 2026-08-13 18:26 UTC

   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. resolved 2026-08-17 11:40 UTC

   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...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elastic Cloud Serverless

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 03:57 UTC

   We are investigating failures with Serverless project creation.

2. investigating 2026-08-13 05:28 UTC

   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...

3. monitoring 2026-08-13 06:04 UTC

   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...

4. resolved 2026-08-13 08:40 UTC

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

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elasticsearch connectivity: GCP asia-south1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. resolved 2026-08-06 17:41 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-05 22:59 UTC

   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...

2. identified 2026-08-05 23:18 UTC

   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...

3. identified 2026-08-06 12:12 UTC

   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. resolved 2026-08-12 08:59 UTC

   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.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 14:24 UTC

   We have identified an issue with our metering of Instance Capacity for Hosted Deployments that affects a subset of customers. We currently believe the impact to be limited to a small number of customers but are still working to identify and correct all occurrences of this issue....

2. investigating 2026-07-21 23:15 UTC

   We are still investigating the metering issue impacting a small number of customers. We will proactively issue billing corrections where necessary. We'll provide another update when new information is available.

3. investigating 2026-07-22 10:49 UTC

   We are still investigating the metering issue impacting a small number of customers. We'll provide a further update when new information is available.

4. resolved 2026-07-22 23:14 UTC

   All metering errors have been corrected. We will be issuing refunds to the small number of affected customers.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: AutoOps

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-21 13:45 UTC

   RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps...

2. resolved 2026-07-21 14:21 UTC

   This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 09:36 UTC

   We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code. Available Workarounds: - Use an alternative MFA...

2. investigating 2026-07-21 10:56 UTC

   Update: This incident is still ongoing and we are continuing to investigate. We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when...

3. investigating 2026-07-21 14:25 UTC

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

4. monitoring 2026-07-21 23:10 UTC

   Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.

5. resolved 2026-07-23 16:37 UTC

   Delivery delays have been resolved, MFA email delivery is fully functional for all customers.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-18 02:45 UTC

   Resolved – This incident is resolved. Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Cloud console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-15 00:15 UTC

   We are investigating errors with our cloud console affecting access to create, update, delete and view Elastic Cloud Hosted deployments. Our team is actively investigating the cause so that they can mitigate and restore the service.

2. monitoring 2026-07-15 00:31 UTC

   The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored

3. resolved 2026-07-15 01:12 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Cloud console

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 12:15 UTC

   We are investigating a problem that prevents customers from authenticating against Elastic Cloud using their Microsoft login credentials

2. resolved 2026-07-13 12:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 00:54 UTC

   We have identified continued impact for a subset of affected customers using EIS. Our team is investigating an issue with the previous remediation and is working to ensure all affected environments are fully restored.

2. monitoring 2026-07-02 02:24 UTC

   The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.

3. resolved 2026-07-02 03:00 UTC

   The incident impacting a subset of customers with EIS in EMEA regions has been resolved. Services have been fully restored and the team has confirmed stability.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure, Google Cloud.

1. investigating 2026-07-01 22:43 UTC

   We are currently investigating a partial outage affecting the Elastic Integration Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.

2. investigating 2026-07-01 22:44 UTC

   We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.

3. investigating 2026-07-01 22:45 UTC

   We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.

4. resolved 2026-07-01 23:05 UTC

   The issue affecting EIS for Elastic Cloud customers with projects or deployments on GCP and Azure in EMEA regions has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-07-01 15:39 UTC

   We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual. What you may notice: Deployment metrics and instance utilization data may not appear in the...

2. identified 2026-07-01 16:50 UTC

   We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.

3. monitoring 2026-07-01 19:50 UTC

   The system has recovered and we are continuing to monitor the situation.

4. resolved 2026-07-01 20:23 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-29 16:32 UTC

   We have identified an issue with our ability to deliver certain static assets to our products. We have identified and are working to implement a fix.

2. identified 2026-06-29 16:33 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-06-29 16:58 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2, Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west4, Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-2, Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-1, Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-2, Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-central-1, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southafricanorth

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-17 15:52 UTC

   We are currently investigating an issue when creating/updating Deployments in several regions. We've identified the issue and working on applying a fix. We will provide an update when one is available or within the hour, whichever comes first.

2. monitoring 2026-06-17 16:53 UTC

   We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.

3. resolved 2026-06-17 17:35 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-06-16 22:54 UTC

   We are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour,...

2. identified 2026-06-17 00:02 UTC

   This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.

3. resolved 2026-06-17 00:59 UTC

   This issue is resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-16 10:57 UTC

   We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud...

2. investigating 2026-06-16 11:21 UTC

   We are continuing to investigate this issue.

3. resolved 2026-06-16 11:36 UTC

   We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elastic Cloud Serverless

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-15 17:31 UTC

   We are currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1. We will continue to update status as we learn more.

2. monitoring 2026-06-15 18:00 UTC

   This issue has been mitigated, and we are continuing to monitor the situation.

3. resolved 2026-06-15 19:13 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-06-04 01:51 UTC

   Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are currently investigating the issue.

2. monitoring 2026-06-04 03:44 UTC

   Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. Recovery has started and we will provide further updates as we progress.

3. monitoring 2026-06-04 06:21 UTC

   Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are seeing increased recovery across as we monitor the situation. Services are being restored. Monitoring is continuing, and we will provide further...

4. resolved 2026-06-04 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Cloud console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-06-02 13:25 UTC

   Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and...

2. investigating 2026-06-02 15:02 UTC

   We are seeing some signs of recovery, and have taken action to mitigate the impact and speed up recovery. Some users will still see seeing missing metrics visualizations in the Cloud console, for deployments in the Azure North Europe region. We are actively investigating and...

3. resolved 2026-06-02 19:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-29 18:00 UTC

   We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.

2. resolved 2026-05-29 18:36 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Power/cooling issues in West US 2.

1. investigating 2026-05-29 06:32 UTC

   We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region. We have confirmed that impact to our service is limited to a single...

2. investigating 2026-05-29 06:35 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-29 06:50 UTC

   We are continuing to investigate this issue.

4. identified 2026-05-29 10:43 UTC

   We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region. We have confirmed that impact to our service is limited to a single...

5. identified 2026-05-29 11:46 UTC

   We continue to respond to an upstream Microsoft Azure outage in Azure West US 2 (azure-westus2), caused by a datacenter power event reported by Azure. Elastic impact remains limited to availability zone westus2-2. Customers with deployments not configured for high availability...

6. identified 2026-05-29 14:26 UTC

   We continue to remediate the impact of an upstream Azure outage in Azure West US 2 (azure-westus2), limited to availability zone westus2-2. Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors,...

7. monitoring 2026-05-29 18:50 UTC

   Remediation is underway and systems are recovering. We continue to monitor the situation and will post an update in the next 2 hours or earlier.

8. monitoring 2026-05-30 06:36 UTC

   We continue to monitor the situation which has mostly recovered. A small number of deployments are still not healthy. Our support team is working on resolving these on a case-by-case basis.

9. resolved 2026-05-31 21:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. resolved 2026-05-26 21:35 UTC

   Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We have already stabilized the situation.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-23 21:42 UTC

   Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and...

2. identified 2026-05-23 22:11 UTC

   The problem has been identified and is being stabilized, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.

3. resolved 2026-05-23 22:26 UTC

   The system has recovered and functionality has returned to normal.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. resolved 2026-05-22 04:54 UTC

   Synthetics browser monitors running in Europe-Germany region (GCP europe-west3) for some of the users were experiencing delayed executions results and some of them being stopped. The issue affected both Elastic Cloud Hosted and Elastic Cloud Serverless in that region and other...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: AutoOps

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-20 15:29 UTC

   We are investigating an issue that prevents new Elastic Cloud customers, including trial users, from accessing AutoOps across all regions. Impact: New customers and trial accounts are currently unable to access the AutoOps dashboard. Existing Customers: Service is unaffected....

2. monitoring 2026-05-20 15:48 UTC

   We have mitigated the issue preventing new Elastic Cloud customers and trial users from accessing AutoOps by restarting a backend service. We are actively monitoring to confirm the fix remains stable and that all new user logins are functioning as expected. We will provide a...

3. monitoring 2026-05-22 16:19 UTC

   We continue to actively monitor the implemented mitigation actions. All new user logins are functioning as expected. A permanent resolution is scheduled to be implemented early next week. Our next update will be once the resolution actions are complete, or sooner if the...

4. resolved 2026-05-27 13:06 UTC

   The permanent resolution has been implemented, thus concluding our resolution actions. This incident is resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elasticsearch Availability

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-05-11 08:00 UTC

   We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable. The root cause of this issue has been identified and resolved - we are...

2. resolved 2026-05-11 11:11 UTC

   We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 18:10 UTC

   We are currently investigating reports that some customers may be facing issues with email alerts.

2. monitoring 2026-05-08 23:11 UTC

   A solution has been implemented, and email delivery has resumed. We are continuing to track the situation closely and will provide another update once considered resolved.

3. resolved 2026-05-09 01:01 UTC

   This issue is now resolved. Email delivery has been successful with no monitored issues.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: AutoOps

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-04-30 21:46 UTC

   We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.

2. monitoring 2026-04-30 22:18 UTC

   This issue has now been resolved and we are continuing to monitor the system.

3. resolved 2026-04-30 22:36 UTC

   This issue has now been resolved.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-04-28 14:46 UTC

   Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the us-east-1 (US East) region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and...

2. investigating 2026-04-28 15:57 UTC

   Our investigation is ongoing. Some early signs of stabilisation have been observed, but metrics visualizations in the Cloud console remain impacted. We will provide a further update within 30 minutes.

3. investigating 2026-04-28 16:32 UTC

   Our investigation is ongoing. We continue to see early signs of stabilization, but metrics visualizations in the Cloud console remain impacted. We will provide a further update in 1 hour, or when there is a change in status.

4. identified 2026-04-28 17:39 UTC

   We are continuing to see signs of stabilization and monitoring as the system recovers, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.

5. resolved 2026-04-28 18:40 UTC

   The system has recovered and functionality has returned to normal.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-04-27 11:49 UTC

   We are currently investigating connectivity issues affecting a subset of customers in our AWS EU West 3 (Paris) region. Some requests may be experiencing elevated latency or failures. Our team is actively investigating, and we are working with our cloud infrastructure provider...

2. identified 2026-04-27 11:57 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-04-27 12:08 UTC

   Our monitoring system reports that AWS EU West 3 (Paris) region ingress layer traffic has recovered to normal levels as of 11:36 UTC and our SLO alerts have resolved. We are continuing to monitor and will update once we are confident the issue is fully resolved.

4. resolved 2026-04-27 12:40 UTC

   The connectivity issues affecting a subset of customers in our AWS EU West (Paris) region have been resolved. Failed probes recovered at 11:36 UTC following remediation of an issue with our underlying cloud infrastructure provider. We are no longer observing any elevated error...

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Affected: Elastic Inference Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-20 06:37 UTC

   We're seeing elevated 5xx error rates for the Gemini Embedding v1 model in EIS. The following default inference endpoint is affected: - .google-gemini-embedding-001 We're investigating and will update again in 2 hours or if there's a change in status.

2. investigating 2026-04-20 09:50 UTC

   Errors are coming from the provider API (Google). The incident has been escalated to them, and we are still waiting for a response.

3. resolved 2026-04-20 10:41 UTC

   An incident with an upstream service provider has been resolved, and access to the model is now restored.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-09 20:46 UTC

   A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.

2. identified 2026-04-09 22:44 UTC

   We have merged a fix and are working on deploying it to production

3. identified 2026-04-10 12:18 UTC

   We are still working on moving the fix to production as we experienced some testing issues.

4. resolved 2026-04-10 19:54 UTC

   We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Elastic Cloud's status page.