Elastic reports multiple service issues

Elastic is dealing with 2 concurrent service issues — tracked live below.

By The Downtime · Sep 9, 2026 · 8:45 PM ·Updated 1 month ago

Elastic has identified a bug in Fleet Server versions 9.5.3 and 9.4.6 that causes Elastic Agents to crash-loop and go offline when Fleet pushes configuration updates. The issue affects only policies configured to use Fleet's remote Elasticsearch output feature and impacts agent enrollment and check-in operations. The current status is identified.

Elastic develops observability and search software used by enterprises for logging, metrics, and analytics across distributed systems.

Elastic recommends that users of Fleet's remote Elasticsearch output avoid upgrading to versions 9.5.3 or 9.4.6 until a fix becomes available. Customers already running affected versions experiencing agent check-in failures should contact Elastic Support for remediation steps. A fix has been merged and will ship in upcoming 9.5.x and 9.4.x releases, with issue tracking in fleet-server#7791 and elastic-agent#16542.

This is a developing story and will be updated as new information becomes available.

⚠️ Issues being tracked (2)

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

Identified

source ↗

Organisation Owner role access to Elastic Cloud Hosted Kibana

Resolved

source ↗

🕒 Live updates (9)

identified Elastic Agent enrollment/check-in failur... Sep 11, 4:00 PM

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 Elastic Agent enrollment/check-in failur... Sep 11, 2:25 PM

resolved Kibana access restored for UI-assigned O... Sep 10, 10:31 PM

This incident has been resolved.

monitoring Kibana access restored for UI-assigned O... Sep 10, 9:51 AM

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 Organisation Owner role access to Elasti... Sep 10, 6:03 AM

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

identified Kibana access restored for UI-assigned O... Sep 10, 6:03 AM

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

identified Organisation Owner role access to Elasti... Sep 10, 1:30 AM

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.

identified Kibana access restored for UI-assigned O... Sep 10, 1:30 AM

identified Elastic Agent enrollment/check-in failur... Sep 9, 8:44 PM

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.

📎 Sources

Elastic status ↗

Outage details are aggregated from official provider status pages. The Downtime reports them as a public service and is not affiliated with the providers named.