Elasticsearch incident: Elevated Error Rates Affecting Managed OTLP

1. resolvedAug 20, 2026, 22:13 UTC

   This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.

2. identifiedAug 20, 2026, 21:59 UTC

   We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline. Based on our investigation, customer workloads were not affected.

3. investigatingAug 20, 2026, 20:53 UTC

   We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. We will provide an update within 1 hour.

4. investigatingAug 20, 2026, 20:22 UTC

   We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. Our team is actively investigating the root cause. We will provide an update within 30 minutes.

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.

• GitHub: Intermittent failures creating agent tasksCritical · Aug 20, 2026, 14:43 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• LiveKit: Investigating reports of elevated egress & connector API errorsMinor · Aug 20, 2026, 21:10 UTC
• Inngest: We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.Minor · Aug 20, 2026, 21:44 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