Provider
Elastic CloudIncident detail
Privatelink hostnames reported by API are incorrect
Privatelink hostnames reported by API are incorrect
Timeline window
to
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
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.
Identified
We have merged a fix and are working on deploying it to production
Identified
We are still working on moving the fix to production as we experienced some testing issues.
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.