Looking for an update now? Check the current status, or follow Elastic Cloud for future changes.
0%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)
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 degraded.
Our teams are continuing to work on mitigation and recovery, and we are working closely with our cloud provider. We do not yet have an estimated time for full recovery.
We will provide the next update by 12:00 UTC, or sooner if there is a significant change.
identified
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, limited signs of recovery, and a small number of the initially affected deployments are recovering. We are continuing our mitigation work and will share more as recovery progresses.
Elastic Serverless: We have taken steps to avoid placing new projects in the affected zone, and we are now rebalancing existing projects to other availability zones. We are seeing signs of recovery - some projects remain unavailable or degraded in the meantime.
Reduced capacity in the region may delay scaling and the creation of new resources. We do not yet have an estimated time for full recovery from our cloud provider. We are working closely with them and will provide the next update by 10:15am UTC.
identified
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 Serverless projects with resources in the affected zone may be unavailable or experience degraded performance.
We have taken steps to avoid placing new Serverless projects in the affected zone, and we are working to restore services that depend on it. Reduced capacity in the region may delay scaling and the creation of new resources.
We do not yet have an estimated time for recovery from our cloud provider. We are working closely with them and will provide the next update within an hour.
investigating
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. Monitoring and logging for deployments in the region may also be delayed.
Deployments in other zones and regions are not affected. Our engineers are actively working on the issue, and we are in contact with our cloud provider.
Delayed or Unavailable project operation in GCP us-central1
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 the situation and will provide another update when more information is available.
identified
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 available.
identified
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 provide another update when more information is available.
investigating
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.
Delayed Serverless Metrics in Azure UAE North region
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
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 mitigation, you can try re-running failed plan changes.
Existing running deployments are not impacted. Our team is actively monitoring the situation and working to mitigate the issue.
We will provide an update in the next 12 hours.
AutoOps node metrics temporarily unavailable in some regions
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 to the remaining affected regions. We'll provide a further update once the rollout is complete.
investigating
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 loss has occurred.
We will provide an update within the next 2 hours or earlier.
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.
investigating
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.
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.
identified
Update: This incident is still ongoing and we are continuing to investigate.
identified
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.
Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output
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 or 9.5.3 before 21:20 UTC on 10 September 2026, perform the following mitigation:
1. Force restart the Integration Server component of you affected deployment
2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart
IMPORTANT: The patched Fleet Server is not available outside Elastic Cloud Enterprise (ECE) Stack Packs and Elastic Cloud Hosted (ECH).
identified
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 or 9.5.3 before 21:20 UTC on 10 September 2026, perform the following mitigation:
1. Force restart the Integration Server component of you affected deployment
2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart
identified
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.
Issue impacting services running in GCP us-central1
We are seeing signs of recovery for services in GCP us-central1 impacted by an <a href='https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev'>upstream CSP issue</a>. We are continuing to monitor the situation and will provide updates as they become available.
identified
An ongoing <a href="https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev">upstream CSP issue</a> 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.
identified
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.
investigating
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.
Legacy Incident Archive
37 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Elevated Error Rates Affecting Managed OTLP
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
Issue when creating Serverless projects in Azure eastus region
majorSource not attested
Last archived state: resolved
View archived record details
Elastic Cloud Serverless
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.
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.1: false-positive matches in certain boolean queries
majorSource not attested
Last archived state: resolved
View archived record details
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 Ser...
Increased error rates for microsoft-multilingual-e5-large
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
investigating
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
Serverless project creation delayed or failing
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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 ...
investigating
We are investigating failures with Serverless project creation.
Elasticsearch 9.5.0 contains a query-correctness defect
majorSource not attested
Last archived state: resolved
View archived record details
identified
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.
identified
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.
identified
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 er...
July 2026
Metering issue with Elastic Cloud Hosted Deployments
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are still investigating the metering issue impacting a small number of customers.
We'll provide a further update when new information is available.
investigating
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.
investigating
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. We will proactively issue billing corrections where necessary.
AutoOps monitoring data not ingested for subset of deployments
majorSource not attested
Last archived state: resolved
View archived record details
identified
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 monitoring data during this timeframe.
Note this incident has already been resolved, and is being posted retroactively.
Elastic Cloud - Email MFA Delivery Delays (Gmail)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
investigating
Update: This incident is still ongoing and we are continuing to investigate.
investigating
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 receiving their email MFA code.
Available Workarounds:
- Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API K...
investigating
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 factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API Key access to your projects and deployments remains fully operational.
We are a...
Cloud Console Deployment Errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
investigating
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.
