Elasticsearch outage: Delayed AutoOps Metrics in AWS us-east-1

Affected components

• AutoOps

1. resolvedApr 30, 2026, 22:36 UTC

   This issue has now been resolved.

2. monitoringApr 30, 2026, 22:18 UTC

   This issue has now been resolved and we are continuing to monitor the system.

3. identifiedApr 30, 2026, 21:46 UTC

   We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.

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.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• LaunchDarkly: Issue with Experiment Results in case of Flag Variation editsMinor · Apr 29, 2026, 20:19 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 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