AutoOps node metrics temporarily unavailable in some regions

What to do

• Check whether your product depends on Elastic Cloud. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 41m it lasted.

  Anything that failed between 2026-09-17 15:50 UTC and 2026-09-17 16:31 UTC may need a replay.

• Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Elastic Cloud 3

1. investigatingSep 17, 2026, 3: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.

   provider

2. identifiedSep 17, 2026, 4: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.

   provider

3. resolvedSep 17, 2026, 4: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.