Privatelink hostnames reported by API are incorrect

Resolved

Major impact

Started

Lasted 23h 8m

View official incident ↗

Updates

  1. 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.

  2. Identified

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

  3. Identified

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

  4. 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.