Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): AutoOps node metrics temporarily unavailable in some regions
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-09-17 16:13 UTC
Public — what happened
Summary
Elastic Cloud (Public) said that node-level metrics in AutoOps, such as CPU, memory, disk and thread pool figures, were missing in some regions starting on 2026-09-17 at 15:50 UTC. The company said cluster health, shard and deployment information stayed available throughout and that no data was lost. Elastic Cloud reported it had found the cause and confirmed a fix in one region before extending it to the other affected regions. The incident is listed as resolved at 16:33.
Timeline
- Started — 2026-09-17 15:50 UTC
- Resolved — 2026-09-17 16:33 UTC · 43 min 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 39, 2026, our weekly internet health report.