Skip to main content
Elastic Cloud

Privatelink hostnames reported by API are incorrect

Partial outage Lasted 23h 8m · started · Elastic Cloud's page

Level
confirmed
Worst impact
Partial outage
Down Index
33of 100

What to do

  • Check whether your product depends on Elastic Cloud. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 23h 8m it lasted.

    Anything that failed between 2026-04-09 20:46 UTC and 2026-04-10 19:54 UTC may need a replay.
  • Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Elastic Cloud 4

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

    provider

  2. identified

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

    provider

  3. identified

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

    provider

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9e8ce30c70

Is Elastic Cloud still down?

No, this incident was resolved 2026-04-10 19:54 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.

How long did it last?

23h 8m, from 2026-04-09 20:46 UTC to 2026-04-10 19:54 UTC, by the times Elastic Cloud posted.

What caused it?

Elastic Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.