Elastic Cloud incident

Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output

Major Ongoing View vendor source →

Elastic Cloud is currently experiencing a major incident, which began 3h ago. The vendor's full update timeline is below.

Started
Sep 09, 2026, 08:44 PM UTC
Resolved
Ongoing
Duration
● 3h 13m
Detected by Pingoru
Sep 09, 2026, 08:44 PM UTC

Update timeline

  1. identified Sep 09, 2026, 08:44 PM 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 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.