Skip to content
Elastic · Data and observabilityApr 9, 2026, 20:46 UTC

Privatelink hostnames reported by API are incorrect

MajorNot disclosedUpdated 19h ago
Apr 9, 20:46 UTCApr 10, 19:54 UTC
Duration
23h 8m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
27 incidents
Affected
Not listed by the vendor.
Status page

Final update

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.

Timeline

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

More from Elastic

Full history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.