Skip to main content
Elastic Cloud

Replication bug causing slow recoveries

Partial outage Lasted 29d 12h · started · Elastic Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
Elastic Cloud Hosted
Down Index
33of 100

What to do

  • Check whether you use Elastic Cloud Elastic Cloud Hosted. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 29d 12h it lasted.

    Anything that failed between 2026-09-01 08:16 UTC and 2026-09-30 20:44 UTC may need a replay.
  • Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We have identified the root cause and the team is working on a fix scheduled to be released in Elasticsearch version 9.
Read the postmortem

Updates from Elastic Cloud 6

  1. investigating

    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.

    provider

  2. identified

    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

    provider

  3. identified

    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.

    provider

  4. monitoring

    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.

    provider

  5. monitoring

    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.

    provider

  6. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-109aa64df4

Is Elastic Cloud still down?

No, this incident was resolved 2026-09-30 20:44 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.

How long did it last?

29d 12h, from 2026-09-01 08:16 UTC to 2026-09-30 20:44 UTC, by the times Elastic Cloud posted.

What was affected?

Elastic Cloud named Elastic Cloud Hosted.

What caused it?

Elastic Cloud wrote: "We have identified the root cause and the team is working on a fix scheduled to be released in Elasticsearch version 9." The postmortem: https://stspg.io/nx73hprsrgph

Where does this come from?

Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.