Companies / Elastic Cloud / incidents
Elastic Cloud: AutoOps node metrics temporarily unavailable in some regions
Elastic Cloud reported a major AutoOps degradation: node-level CPU, memory, disk and thread pool metrics were missing in some regions from 2026-09-17 15:50 UTC to 2026-09-17 16:31 UTC (41 min). A validated fix was rolled out; cluster health, shard and deployment data were unaffected, with no data loss.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- investigating
We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data loss has occurred. We will provide an update within the next 2 hours or earlier.
- identified
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.
- resolved
The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.
Rewindex changes for this incident
- Major incident: AutoOps node metrics temporarily unavailable in some regions 2026-09-17 15:50 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Elastic Cloud profile · Recent Elastic Cloud incidents · Markdown · JSON