Changes / Elastic Cloud / AutoOps monitoring data not ingested for subset of deployments
Elastic Cloud: Major incident: AutoOps monitoring data not ingested for subset of deployments
Summary
Elastic Cloud reported major AutoOps degradation: a subset of Elastic Agents could not report metrics across all regions during Jul 18 02:40 UTC–Jul 20 14:00 UTC, leaving monitoring gaps. The issue was corrected and data resumed normally. Posted retroactively, the resolved incident record started 2026-07-21 13:45 UTC, with a computed duration of 35 min.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 56%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: AutoOps monitoring data not ingested for subset of deployments
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-07-21 13:45 UTC
Before: not present
After: 2026-07-21 14:21 UTC
Before: not present
After: AutoOps, Global services - AutoOps
Before: not present
After: RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.
Note this incident has already been resolved, and is being posted retroactively.
Before: not present
After: This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: AutoOps monitoring data not ingested for subset of deployments (this change) Elastic Cloud reported major AutoOps degradation: a subset of Elastic Agents could not report metrics across all regions during Jul 18 02:40 UTC–Jul 20 14:00 UTC, leaving monitoring gaps. The issue was corrected and data resumed normally. Posted retroactively, the resolved incident record started 2026-07-21 13:45 UTC, with a computed duration of 35 min. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON