Resolved incident

Privatelink hostnames reported by API are incorrect

Elastic · Major · Started

Duration
23h 8m
Severity
Major
Status
Resolved

Summary

Major · 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.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Identified

    Elastic

    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.

  2. Identified

    Elastic

    We have merged a fix and are working on deploying it to production

  3. Identified

    Elastic

    We are still working on moving the fix to production as we experienced some testing issues.

  4. Resolved

    Elastic

    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.