Elastic Cloud incident
Privatelink hostnames reported by API are incorrect
Resolved after 23 hours 7 minutes, on April 9, 2026.
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.
Update timeline
- identified Apr 09, 2026, 08:46 PM 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.
- identified Apr 09, 2026, 10:44 PM UTC
We have merged a fix and are working on deploying it to production
- identified Apr 10, 2026, 12:18 PM UTC
We are still working on moving the fix to production as we experienced some testing issues.
- resolved Apr 10, 2026, 07:54 PM 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.
Your product runs on more than Elastic Cloud
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services