A recent change to Elastic Cloud's Privatelink implementation caused the deployment API to report incorrect URLs, resulting in connectivity issues for customers relying on those URLs. The incident lasted 23.2 hours and affected customers' ability to connect to their deployments through Privatelink. The issue was resolved by deploying a fix to the User Console that corrected the hostname reporting.
Trusted by 1000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the moment something breaks.
Ready to take control?
Start Free TrialWe 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.
We are still working on moving the fix to production as we experienced some testing issues.
We have merged a fix and are working on deploying it to production
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with