Outage in AWS Databricks
ES-1895876
Resolved Minor
May 05, 2026 - Started 8 days ago
- Lasted about 3 hours
Incident Report
Summary AI Generated
AWS Databricks Classic Compute experienced cluster startup failures across multiple regions for 3.3 hours starting at 03:33 UTC on May 5, 2026, specifically affecting clusters with configured init scripts. The root cause was an outage in an external Ubuntu package repository, which was restored by the external provider at 08:06 UTC. Customers experienced clusters failing to initialize, not starting at all, or extended startup times during the incident.
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
AWS 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 )
8 days ago - at 05/05/2026 07:40AM
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.
8 days ago - at 05/05/2026 09:22AM
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 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 AWS Databricks outages
ES-1903956 - 5 days ago
ES-1882222 - 16 days ago
ES-1873238 - 21 days ago
ES-1868544 - 22 days ago
ES-1864534 - 23 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
