Skip to content
OutageDeck

Incident detail

Privatelink hostnames reported by API are incorrect

Resolved incidentMajor

Timeline window

to

Outage alerts

Get alerted the next time Elastic Cloud breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Elastic Cloud alerts work

Timeline

Incident updates

Every update Elastic Cloud posted, oldest to newest, exactly as it appeared on their official status page.

  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.

  2. Identified

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

  3. Identified

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

  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.

Keep exploring

More from Elastic Cloud

Neighboring incidents on Elastic Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Connection issue to Kibana via the Cloud UI SSO

Newer incident →

EIS elevated 5xx error rates for model google-gemini-embedding-001

All Elastic Cloud incidentsElastic Cloud live status