Databricks Azure experienced a minor incident on May 5, 2026 affecting Compute and Unity Catalog (Canada Central) and 1 more component, lasting 4h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 05, 2026, 07:36 AM UTC
Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 05:55 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified May 05, 2026, 09:17 AM UTC
Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations If the workload rely on packages that are available via alternate mirror repositories, customer may consider temporarily updating init script to use an alternative mirror. For example, customers previously using archive.ubuntu.com can use azure.archive.ubuntu.com as an alternative mirror, where applicable. Similar alternatives may be available depending on your environment and configuration. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 08:06 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring May 05, 2026, 10:51 AM UTC
Impact Summary Between 03:33 UTC and 08:06 UTC on 05 May 2026 , Classic Compute in multiple regions may have failed to start clusters when init scripts configured. There was brief recovery observed at 05:55 UTC. Full recovery was observed at 08:06 UTC. Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status The issue has been mitigated. We are continuing to monitor for any residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.