Elasticsearch incident: AutoOps monitoring data not ingested for subset of deployments

1. resolvedJul 18, 2026, 02:45 UTC

   Resolved – This incident is 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Elasticsearch's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Twilio: SMS Delivery Failures from Twilio to Vodafone AustraliaMinor · Jul 13, 2026, 02:47 UTC
• Grafana Cloud: Issue with Dashboard Views Being RegisteredMinor · Jul 14, 2026, 08:10 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Twilio: SMS Delivery Failures from Twilio to MTS RussiaMinor · Jul 17, 2026, 04:13 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Long Codes to Chunghwa TaiwanMinor · Jul 17, 2026, 14:10 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Reliance Jio IndiaMinor · Jul 17, 2026, 15:54 UTC
• Grafana Cloud: Grafana Cloud login issues for users with role of NoneMinor · Jul 17, 2026, 18:22 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 22 incidents in the last 90 days, 21 of them major or critical. A typical incident lasted 5h 53m. See Elasticsearch's uptime and incident history