Elastic Status · History · Incident #5735
RESOLVEDAutoOps monitoring data not ingested for subset of deployments
Major · Started Jul 21, 2026 · 1:45 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Elastic Status · History · Incident #5735
RESOLVEDMajor · Started Jul 21, 2026 · 1:45 PM
Duration
35m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Started
Jul 21, 2026 · 1:45 PM
Resolved
Jul 21, 2026 · 2:21 PM
Duration
35m
Severity
Major
Event timeline
Identified
Jul 21 · 1:45 PM ElasticRESOLVED - 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.
Resolved
Jul 21 · 2:21 PM ElasticThis incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.