Starting at approximately 10:10 UTC on August 6, 2026, AWS Databricks experienced a capacity-related incident lasting around 2.5 hours, causing failures and delays in starting Serverless and Classic Compute resources, SQL warehouses, and Lakeflow Declarative Pipelines. The root cause was identified as a memory exhaustion issue that caused system components to restart repeatedly. Engineering teams identified the root cause and were actively mitigating the issue while monitoring for recurring intermittent errors.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We are actively investigating an issue affecting Databricks compute.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute resources, including SQL warehouses.
Symptoms
• Serverless SQL warehouses failing to start
• Classic compute SQL warehouses failing to start
• Delays or errors during compute cluster startup
Recommendations
No customer action is required at this time.
Current Status
The incident is under active investigation as the team works to identify the root cause of Serverless Compute startup failures.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Lakeflow Declarative Pipelines.
Symptoms
• Serverless SQL warehouses failing to start
• Classic compute SQL warehouses failing to start or experiencing intermittent delays
• Lakeflow Declarative Pipelines failing
Recommendations
No customer action is required at this time.
Current Status
The incident remains under active investigation, with engineering teams working to identify the root cause and mitigate capacity-related startup failures affecting Serverless Compute, Classic Compute, and Lakeflow Declarative Pipelines.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Lakeflow Declarative Pipelines.
Symptoms
• Serverless SQL warehouses failing to start
• Classic compute SQL warehouses failing to start or experiencing intermittent delays
• Lakeflow Declarative Pipelines failing
Recommendations
No customer action is required at this time.
Current Status
The root cause has been identified as a capacity issue that caused some system components to run out of available memory and to restart repeatedly. Engineering continues active mitigation while monitoring for intermittent errors recurring across affected services.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
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