Companies / Elastic Cloud / incidents
Elastic Cloud: Privatelink hostnames reported by API are incorrect
Elastic Cloud reported a major incident starting 2026-04-09 20:46 UTC: a recent Privatelink implementation change caused the deployment API to return incorrect URLs in some cases, disrupting connectivity for customers relying on them. Resolved at 2026-04-10 19:54 UTC after 23 h 7 min, the incident ended with a fix deployed to the User Console to restore correct hostnames.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- 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.
Rewindex changes for this incident
- Major incident: Privatelink hostnames reported by API are incorrect 2026-04-09 20:46 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Elastic Cloud profile · Recent Elastic Cloud incidents · Markdown · JSON