# Privatelink hostnames reported by API are incorrect

- Provider: [Elastic Cloud](https://down.guide/providers/elastic-cloud)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 23h 8m
- started 2026-04-09 20:46 UTC
- id: DWN-9e8ce30c70
- Official page: https://stspg.io/ycwz074xy7tr

## Updates from Elastic Cloud
### 2026-04-09 20:46 UTC: 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.

### 2026-04-09 22:44 UTC: identified
We have merged a fix and are working on deploying it to production

### 2026-04-10 12:18 UTC: identified
We are still working on moving the fix to production as we experienced some testing issues.

### 2026-04-10 19:54 UTC: 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.

From the builder: does your app depend on Elastic Cloud? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=elastic-cloud) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Elastic Cloud.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-9e8ce30c70), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.