Skip to content

Incident detail

Unable to start PrivateLink-enabled engines in Azure

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Dremio breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    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.

  2. Identified

    We have identified the issue and are working on mitigating the issue. We will provide another update within the next 30 minutes.

  3. Monitoring

    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.

  4. Resolved

    We have verified engines are able to scale up correctly. We apologize for any inconvenience caused.

Keep exploring

More from Dremio

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