Changes / Elastic Cloud / Privatelink hostnames reported by API are incorrect
Elastic Cloud: Major incident: Privatelink hostnames reported by API are incorrect
Summary
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Privatelink hostnames reported by API are incorrect
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-09 20:46 UTC
Before: not present
After: 2026-04-10 19:54 UTC
Before: not present
After: 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.
Before: not present
After: We have merged a fix and are working on deploying it to production
Before: not present
After: We are still working on moving the fix to production as we experienced some testing issues.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Privatelink hostnames reported by API are incorrect (this change) 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. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON