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

Affected components

• AutoOps

1. resolvedJul 21, 2026, 14:21 UTC

   This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.

2. identifiedJul 21, 2026, 13:45 UTC

   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.

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
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• PlanetScale: Insights metrics underreportingMinor · Jul 20, 2026, 18:29 UTC
• Sentry: Delayed ingestion on us regionMinor · Jul 21, 2026, 10:30 UTC
• Tailscale: Control D Integration IssuesMinor · Jul 21, 2026, 13:43 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 23 incidents in the last 90 days, 20 of them major or critical. A typical incident lasted 3h 35m. See Elasticsearch's uptime and incident history