Elastic.io incident

Privatelink hostnames reported by API are incorrect

Major Resolved View vendor source →

Elastic.io experienced a major incident on April 9, 2026, lasting 23h 7m. The incident has been resolved; the full update timeline is below.

Started
Apr 09, 2026, 08:46 PM UTC
Resolved
Apr 10, 2026, 07:54 PM UTC
Duration
23h 7m
Detected by Pingoru
Apr 09, 2026, 08:46 PM UTC

Update timeline

  1. identified Apr 09, 2026, 08:46 PM 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.

  2. identified Apr 09, 2026, 10:44 PM UTC

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

  3. identified Apr 10, 2026, 12:18 PM UTC

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

  4. resolved Apr 10, 2026, 07:54 PM 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.