Incidentsby GlyphUnable to start PrivateLink-enabled engines in Azure
May 8, 16:07 UTCMay 8, 19:16 UTC
Duration
3h 9m
Impact
Informational
Root cause
Not disclosed
Dremio, 90 days
2 incidents
Affected
Dremio Cloud - Europe
Final update
We have verified engines are able to scale up correctly. We apologize for any inconvenience caused.
Timeline
- Resolved · May 8, 19:16 UTC
We have verified engines are able to scale up correctly. We apologize for any inconvenience caused.
- Monitoring · May 8, 16:38 UTC
We have applied a mitigation for the issue. We are continuing to monitor the health of the environment and are seeing engines recover. We apologize for any inconvenience caused.
- Identified · May 8, 16:24 UTC
We have identified the issue and are working on mitigating the issue. We will provide another update within the next 30 minutes.
- Investigating · May 8, 16:07 UTC
Azure engines configured to use PrivateLink may be unable to start in Dremio Cloud. We are currently investigating and will provide another update in 30 minutes.
More from Dremio
Full historyQuery failures in Dremio Cloud (US & EU)lasted 0mEngine scaling issues in Dremio Cloud (US)lasted 30mDremio Cloud US app and login unavailablelasted 4h 51mQuery failures in Dremio Cloud (US)lasted 0mNetwork Connectivity Errors in Dremio Cloud (US)lasted 0mEmail delivery failures in Dremio Cloud (EU)lasted 3d 21h