Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-09-11 16:00 UTC
Public — what happened
Summary
Elastic Cloud reported a major issue in which Elastic Agents could fail to enroll or check in when running Fleet Server versions 9.5.3 or 9.4.6 with a remote Elasticsearch output configured, beginning on September 9, 2026 at 20:44 UTC. The company said it shipped corrected builds of both Fleet Server versions as of 21:20 UTC on September 10, so anyone upgrading to those versions now gets the fix. Customers who upgraded before that time were advised to force a restart of their deployment's Integration Server and, if agents still stayed offline, follow a cleanup procedure Elastic published. Elastic noted the patched Fleet Server is only available through Elastic Cloud Hosted and Elastic Cloud Enterprise Stack Packs, and the incident was marked resolved on September 17.
Timeline
- Started — 2026-09-09 20:44 UTC
- Resolved — 2026-09-17 10:32 UTC · 8 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Elastic Cloud (Public) report →
More from Elastic Cloud (Public)
Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.