Elasticsearch outage: Privatelink hostnames reported by API are incorrect

1. resolvedApr 10, 2026, 19:54 UTC

   We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience.

2. identifiedApr 10, 2026, 12:18 UTC

   We are still working on moving the fix to production as we experienced some testing issues.

3. identifiedApr 9, 2026, 22:44 UTC

   We have merged a fix and are working on deploying it to production

4. identifiedApr 9, 2026, 20:46 UTC

   A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.

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.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• Datadog: Notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie are not deliveredMajor · Apr 10, 2026, 14:54 UTC
• RevenueCat: Scheduled Data Exports delayed for GCPMinor · Apr 10, 2026, 07:49 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