Outage in Azure Databricks
ES-1895876
Resolved Minor
May 05, 2026 - Started 12 days ago
- Lasted about 3 hours
Incident Report
Summary AI Generated
Azure Databricks Classic Compute clusters failed to start or experienced extended initialization times when init scripts were configured, affecting multiple regions from 03:33 UTC on May 5, 2026. The issue was caused by an outage at an external Ubuntu package repository that clusters depend on for initialization. The external provider restored service by 08:06 UTC, resolving the 3.3-hour incident after some intermittent recovery periods.
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.
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.
Components affected
Azure Databricks Compute ServiceTrusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
12 days ago - at 05/05/2026 07:36AM
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.
12 days ago - at 05/05/2026 09:17AM
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.
Latest Azure Databricks outages
ES-1916375 - 3 days ago
ES-1893276 - 14 days ago
ES-1885183 - 18 days ago
ES-1852958 - 19 days ago
ES-1882222 - 19 days ago
Never miss outages in third-party dependencies
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
