Major incident

Elastic Cloud (Public): Privatelink hostnames reported by API are incorrect

Current status of Elastic Cloud (Public): Partial outage — live Elastic Cloud (Public) status

Timeline

1. Apr 9, 2026, 20:46 UTC
   identified
   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.
2. Apr 9, 2026, 22:44 UTC
   identified
   We have merged a fix and are working on deploying it to production
3. Apr 10, 2026, 12:18 UTC
   identified
   We are still working on moving the fix to production as we experienced some testing issues.
4. Apr 10, 2026, 19:54 UTC
   resolved
   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.

Updates as published by Elastic Cloud (Public) (original).