Elastic Cloud incident

AutoOps node metrics temporarily unavailable in some regions

Resolved after 41 minutes, on September 17, 2026.

resolved Sep 17, 2026, 04:31 PM UTC

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.

Started
Sep 17, 2026, 03:50 PM UTC
Resolved
Sep 17, 2026, 04:31 PM UTC
Duration
41m
Detected by Pingoru
Sep 17, 2026, 03:50 PM UTC

Update timeline

  1. investigating Sep 17, 2026, 03:50 PM UTC

    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.

  2. identified Sep 17, 2026, 04:13 PM UTC

    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.

  3. resolved Sep 17, 2026, 04:31 PM UTC

    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.

Your product runs on more than Elastic Cloud

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →