Live / Incidents / Elastic Cloud (Public)
Elastic Cloud (Public): AutoOps node metrics temporarily unavailable in some regions
Elastic Cloud (Public) · elastic.coImpact: majorResolved2026-09-17 16:13 UTC
Public — what happened
Summary
We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred.
A fix has been validated in one region and is now being rolled out to the remaining affected regions. We'll provide a further update once the rollout is complete.
Timeline
- Started — 2026-09-17 15:50 UTC
- Last update — 2026-09-17 16:13 UTC
- Resolved — 2026-09-17 16:33 UTC
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 →