Elasticsearch outage: [RESOLVED - 2026-08-26] APM endpoints for serverless projects not available

1. resolvedAug 27, 2026, 18:33 UTC

   This is now resolved

2. monitoringAug 27, 2026, 17:11 UTC

   On August 26, at around 00:00 UTC we deployed a change in Managed Inputs that affected some rules in our internal DNS provider, removing the .apm endpoints some of our Serverless customers. The service was restored around 9AM UTC on the same day. During this time, some customers would have experienced unavailability of the .apm endpoint, for a period in the 9 hour window. We are putting some checks and alerts in place to ensure this does not happen again.

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.

• Supabase: Increased response times for requestsMajor · Aug 27, 2026, 17:20 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Supabase: pgBouncer issues on some older projectsMinor · Aug 26, 2026, 19:49 UTC
• GitHub: Disruption with GitHub BillingMinor · Aug 26, 2026, 23:37 UTC
• Contentful: Daily audit logs outageMinor · Aug 27, 2026, 16:26 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