Incidentsby GlyphPrivatelink hostnames reported by API are incorrect
Apr 9, 20:46 UTCApr 10, 19:54 UTC
Duration
23h 8m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Apr 10, 19:54 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.
- Identified · Apr 10, 12:18 UTC
We are still working on moving the fix to production as we experienced some testing issues.
- Identified · Apr 9, 22:44 UTC
We have merged a fix and are working on deploying it to production
- Identified · Apr 9, 20:46 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.
More from Elastic
Full historymOLTP PrivateLink connectivity issuelasted 13h 28mElastic Support Portal is unavailablelasted 2h 29m403 error when trying to access Autoops in newly created serverless projectslasted 9h 31mElastic Cloud scaling issues in Azurelasted 6h 57mDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)lasted 15h 3mDelayed or Unavailable project operation in GCP us-central1lasted 8h 12m