Elastic Cloud change history

A major outage caused delayed or unavailable operations for some Elastic Cloud Serverless projects in GCP us-central1 from 2026-10-08 16:42 UTC to 2026-10-09 00:54 UTC, lasting 8 h 11 min. Elastic identified an upstream cloud storage issue; the provider applied mitigations, and project operations returned to normal.

Elastic Cloud reported a major incident delaying Cloud UI metrics for Serverless projects in Azure UAE North, starting 2026-10-06 14:04 UTC and resolved at 2026-10-06 17:54 UTC (3 h 50 min). At resolution, delayed “Usage and performance” metrics were recovering and queued usage records were being processed; no data loss was expected.

Elastic Cloud reported major provisioning delays affecting new deployments, scaling, and maintenance-related instance relocations due to an external container image provider’s slowness; existing running deployments were unaffected. It started at 2026-09-23 14:04 UTC and resolved at 2026-09-23 16:03 UTC, lasting 1 h 58 min. Customers could retry failed plan changes as mitigation.

Elastic Cloud reported a major AutoOps degradation: node-level CPU, memory, disk and thread pool metrics were missing in some regions from 2026-09-17 15:50 UTC to 2026-09-17 16:31 UTC (41 min). A validated fix was rolled out; cluster health, shard and deployment data were unaffected, with no data loss.

Some customers could not access the Elastic Support Portal during a major-impact incident starting 2026-09-16 13:17 UTC, resolved at 2026-09-16 15:38 UTC after 2 h 21 min. Elastic investigated with its provider and directed customers to support@elastic.co; access recovered and remained stable.

Elastic Cloud reported a major metrics ingestion delay affecting the Cloud Console in GCP us-east4 from 2026-09-12 23:21 UTC to 2026-09-13 07:45 UTC, lasting 8 h 24 min. The vendor fixed the cause and processed all queued data; metrics were showing in real time at resolution.

A major outage blocked Kibana access on Hosted deployments for UI-assigned Organization Owners with Cloud Console, Elasticsearch, and Kibana access. It started at 2026-09-10 01:30 UTC and lasted 21 h 0 min, resolving at 2026-09-10 22:31 UTC. Elastic identified a permissions management UI bug and restored access through a production fix and affected-account data correction.

A major incident caused Elastic Agents using Fleet's remote Elasticsearch output to crash-loop or fail enrollment/check-in after configuration updates on Fleet Server 9.5.3 and 9.4.6. It ran from 2026-09-09 20:44 UTC to 2026-09-17 10:30 UTC (7 days 13 h). Corrected releases 9.5.4 / 9.4.6 fixed the issue; all known affected deployments recovered.

Elastic Cloud reported a major incident with elevated error rates for Anthropic Claude Haiku 4.5, OpenAI GPT-5.6, and Google Gemini 2.5 Flash on Elastic Inference Service in EU regions, citing 21:50–23:42 UTC. It was resolved; recorded start and resolution were both 2026-09-02 00:04 UTC (computed duration: 0 min).

A major outage impacted Elastic Cloud Hosted and Serverless projects in GCP us-central1 and the Docker Registry service. It started at 2026-09-01 15:18 UTC and was resolved at 2026-09-01 20:05 UTC, lasting 4 h 47 min; Elastic attributed the disruption to an upstream CSP issue.

Elastic Cloud Hosted reported major degradation from 2026-09-01 08:16 UTC to 2026-09-30 20:44 UTC (29 days 12 h). In Elasticsearch 9.5.0, 9.5.1 and 9.5.2, bulk indexing could cause replica divergence, high disk usage and long-running recoveries. Elastic fixed the bug in 9.5.3 and advised affected customers to upgrade and follow workaround steps.

Some Serverless customers’ .apm endpoints were unavailable after a Managed Inputs change removed internal DNS rules. The major incident was recorded from 2026-08-27 17:11 UTC to 2026-08-27 18:33 UTC (1 h 22 min), resolved. The update instead described disruption within a 9 hour window on August 26, with service restored around 9AM UTC that day.

Elastic Cloud reported a major incident affecting new Serverless project initialization in Azure eastus, causing longer creation times due to an upstream Azure storage component issue. It started at 2026-08-20 12:48 UTC and lasted 3 h 34 min, resolving at 2026-08-20 16:22 UTC after Azure's storage issues were resolved and creation times returned to normal.

Elastic Cloud reported a major Elasticsearch 9.5.1 issue causing false-positive matches in boolean queries combining multi-value terms in must, filter, or should clauses with must_not on fields with disabled indexing. It ran from 2026-08-14 09:22 UTC to 2026-08-20 17:09 UTC (6 days 7 h); Elasticsearch 9.5.2 fixes it, and customers on 9.5.0 or 9.5.1 should upgrade.

Elastic Cloud reported a major incident starting 2026-08-13 08:32 UTC, lasting 4 days 3 h, with search embedding failures for microsoft-multilingual-e5-large due to upstream provider issues. Resolved 2026-08-17 11:40 UTC, the model was retired from Elastic Inference Service; requests now return errors, and customers must create custom inference endpoints using their own API keys.

Elastic Cloud reported a major outage delaying or failing Serverless project creation and settings changes through the Cloud UI or API; running projects continued operating normally. It started at 2026-08-13 03:57 UTC and was resolved at 2026-08-13 08:40 UTC, lasting 4 h 42 min. A fix was deployed by 06:04 UTC; no cause was stated.

Elastic Cloud reported major Elasticsearch connectivity latency in GCP asia-south1 (Mumbai), with possible customer impact on 2026-08-06 between 0900 - 1200 UTC. The incident record started and resolved at 2026-08-06 17:41 UTC (computed duration: 0 min); the vendor said the cause was identified and mitigated but provided no details.

Elastic Cloud reported a major Elasticsearch 9.5.0 defect: boolean queries combining must, filter, or should with must_not on unindexed fields could return false positives and inflated counts. It lasted from 2026-08-05 22:59 UTC to 2026-08-12 08:59 UTC (6 days 10 h); Elasticsearch 9.5.1 fixed it, and customers running 9.5.0 were advised to upgrade.

Elastic Cloud reported a major Instance Capacity metering issue affecting a small number of Hosted Deployments customers, starting 2026-07-21 14:24 UTC and lasting 32 h 50 min. Resolved at 2026-07-22 23:14 UTC, all metering errors were corrected, and Elastic said it would issue refunds to affected customers.

Elastic Cloud reported major AutoOps degradation: a subset of Elastic Agents could not report metrics across all regions during Jul 18 02:40 UTC–Jul 20 14:00 UTC, leaving monitoring gaps. The issue was corrected and data resumed normally. Posted retroactively, the resolved incident record started 2026-07-21 13:45 UTC, with a computed duration of 35 min.

Elastic Cloud reported a major incident causing delayed or failed email MFA code delivery for Gmail users, starting 2026-07-21 09:36 UTC and resolved 2026-07-23 16:37 UTC (2 days 7 h). Delays were mitigated on 07-21 23:10 UTC; customers could use registered TOTP/WebAuthn factors or “Log in with Google” as workarounds.

Elastic Cloud reported a major Cloud Console incident affecting access to create, update, delete and view Elastic Cloud Hosted deployments. It started at 2026-07-15 00:15 UTC; management access was restored at 00:31 UTC, and the incident was resolved at 2026-07-15 01:12 UTC, with a reported duration of 56 min.

Elastic Inference Service (EIS) had a major-impact partial outage affecting Elastic Cloud projects or deployments on GCP and Azure in EMEA regions. It started at 2026-07-01 22:43 UTC and was resolved at 2026-07-01 23:05 UTC, lasting 21 min; no cause or fix was stated.

Elastic Cloud reported a major outage affecting deployment creation/updates in AWS eu-central-1, eu-west-2, us-west-1, us-east-2; Azure azure-southafricanorth, azure-eastus2; and GCP europe-west4. It started at 2026-06-17 15:52 UTC and resolved at 2026-06-17 17:35 UTC, lasting 1 h 42 min. A fix was deployed by 06-17 16:53 UTC.

Elastic Cloud reported a major ingestion outage affecting Managed OTLP (mOTLP) and Managed Intake Service (.amp) endpoints in Azure Australia East. It started at 2026-06-16 22:54 UTC and was resolved at 2026-06-17 00:59 UTC, lasting 2 h 4 min; upstream providers were working to resolve it, but no specific cause or fix was stated.

A major Kibana authentication outage affected Deployments and Projects: the "Log in with Elastic Cloud" button failed. It started at 2026-06-16 10:57 UTC and was resolved at 2026-06-16 11:36 UTC, lasting 38 min. Customers could use the Kibana link inside the Elastic Cloud console as a workaround; Elastic reported identifying the root cause and mitigating the issue.

Elastic Cloud reported a major incident in AWS us-east-1 that could intermittently make Elastic Cloud Serverless projects unavailable or prevent new project creation. It ran from 2026-06-15 17:31 UTC to 2026-06-15 19:13 UTC, lasting 1 h 42 min; Elastic reported mitigation at 18:00 UTC and subsequent resolution.

Elastic Cloud reported a major incident causing delays creating Azure serverless projects and possible temporary unavailability of existing Azure projects. It started at 2026-06-04 01:51 UTC and was resolved at 2026-06-04 09:20 UTC, lasting 7 h 28 min; recovery began during monitoring, but no cause was stated.

Elastic Cloud reported a major incident preventing creation of Serverless projects in AWS ap-southeast-2. It started at 2026-05-29 18:00 UTC and was resolved at 2026-05-29 18:36 UTC, with a computed duration of 35 min; no cause or specific fix was stated.

An upstream Azure outage caused major degradation in Azure West US 2 (azure-westus2), limited to westus2-2, including Elastic Serverless projects. Non-high-availability deployments experienced connectivity errors, degraded performance and deployment-operation delays. The incident lasted 2 days 15 h, from 2026-05-29 06:32 UTC to 2026-05-31 21:33 UTC, with remediation and case-by-case support before resolution.

Some users experienced missing metrics visualizations in the Elastic Cloud console for deployments in Azure Southeast Asia due to disrupted metric data ingestion. Elastic rated the impact major and reported the situation stabilized; the incident started and was resolved at 2026-05-26 21:35 UTC, with a recorded duration of 0 min.

Elastic Cloud reported a major degradation in Azure North Europe: disrupted metric data ingestion left some users missing recent metrics in Cloud console charts and monitoring views. It started at 2026-05-23 21:42 UTC and lasted 44 min, resolving at 2026-05-23 22:26 UTC when the system recovered and functionality returned to normal.

Some Synthetics browser monitors in Europe-Germany (GCP europe-west3) had delayed execution results or stopped, affecting Elastic Cloud Hosted and Elastic Cloud Serverless; other regions were unaffected. Elastic Cloud marked the impact major, with start and resolution both at 2026-05-22 04:54 UTC (computed duration: 0 min).

Elastic Cloud reported a major outage affecting multiple Serverless projects, including AWS - N.Virginia (us-east-1) Elasticsearch Availability. Search, Ingest and EIS may have been unavailable from 08:00 UTC to 09:40 UTC on May 11. The incident started at 2026-05-11 08:00 UTC and was resolved at 2026-05-11 11:11 UTC, lasting 3 h 11 min; Elastic stated the root cause was resolved.

Elastic Cloud reported a major incident affecting email alerts for some customers, starting 2026-05-08 18:10 UTC and resolved at 2026-05-09 01:01 UTC, lasting 6 h 50 min. A solution was implemented and email delivery resumed by 05-08 23:11 UTC; the final update confirmed successful delivery with no monitored issues.

Elastic Cloud reported a major degradation causing delayed AutoOps metrics for customers in AWS us-east-1, starting 2026-04-30 21:46 UTC and lasting 50 min until resolution at 2026-04-30 22:36 UTC. The vendor reported the issue fixed and under monitoring at 04-30 22:18 UTC; no cause or specific fix was stated.

Elastic Cloud reported a major degradation in US East (us-east-1): disrupted metric data ingestion left some users missing recent metrics in Cloud console charts and monitoring views. It started at 2026-04-28 14:46 UTC and was resolved at 2026-04-28 18:40 UTC, lasting 3 h 53 min; the system recovered and functionality returned to normal.

Elastic Cloud reported a major connectivity degradation affecting some customers’ APM, Elasticsearch and Kibana in AWS Paris (eu-west-3), causing latency and request failures. The incident started at 2026-04-27 11:49 UTC and was resolved at 2026-04-27 12:40 UTC (51 min). Elastic attributed recovery to remediation of an underlying cloud infrastructure provider issue; other regions were unaffected.

Elastic Cloud reported a major Elastic Inference Service incident affecting .google-gemini-embedding-001, with elevated 5xx errors starting at 2026-04-20 06:37 UTC and lasting 4 h 4 min. Errors came from Google's provider API; the upstream incident was resolved and model access restored at 2026-04-20 10:41 UTC.

Elastic Cloud reported a major incident starting 2026-04-09 20:46 UTC: a recent Privatelink implementation change caused the deployment API to return incorrect URLs in some cases, disrupting connectivity for customers relying on them. Resolved at 2026-04-10 19:54 UTC after 23 h 7 min, the incident ended with a fix deployed to the User Console to restore correct hostnames.

Elastic Cloud reported a major outage affecting Kibana connections through the Cloud UI via SAML SSO for PrivateLink customers only. It started at 2026-04-09 15:37 UTC and was resolved at 2026-04-10 11:51 UTC, lasting 20 h 14 min; a fix was rolled out at 04-09 19:50 UTC, with no further customer impact expected.

Elastic Cloud reported a major Synthetics degradation in us-east-4: some customer monitor jobs may not have run on schedule. The incident started at 2026-04-06 17:58 UTC and was resolved at 2026-04-06 20:43 UTC, lasting 2 h 45 min; Elastic stated the issue was fixed with no further customer impact.