Databricks AWS experienced a minor incident on August 6, 2026 affecting Compute and Lakeflow and 1 more component, lasting 3h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 06, 2026, 10:55 AM UTC
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.
- investigating Aug 06, 2026, 10:55 AM UTC
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.
- investigating Aug 06, 2026, 11:06 AM UTC
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.
- investigating Aug 06, 2026, 11:06 AM UTC
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.
- investigating Aug 06, 2026, 12:02 PM UTC
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.
- investigating Aug 06, 2026, 12:02 PM UTC
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.
- identified Aug 06, 2026, 12:54 PM UTC
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.
- identified Aug 06, 2026, 12:54 PM UTC
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.
- monitoring Aug 06, 2026, 01:21 PM UTC
Between 10:10 UTC and 13:00 UTC on August 6, 2026, a subset of customers using Databricks may have experienced failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Declarative Pipelines. Impact varied in severity and duration across the affected services during this window. Symptoms • Serverless SQL warehouses failed to start or experienced startup delays • Classic compute SQL warehouses failed to start or experienced intermittent delays • Declarative Pipelines experienced execution failures Current Status The issue has been mitigated, and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Aug 06, 2026, 01:21 PM UTC
Between 10:10 UTC and 13:00 UTC on August 6, 2026, a subset of customers using Databricks may have experienced failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Declarative Pipelines. Impact varied in severity and duration across the affected services during this window. Symptoms • Serverless SQL warehouses failed to start or experienced startup delays • Classic compute SQL warehouses failed to start or experienced intermittent delays • Declarative Pipelines experienced execution failures Current Status The issue has been mitigated, and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- resolved Aug 06, 2026, 02:04 PM UTC
Between 10:10 UTC and 13:00 UTC on August 6, 2026, a subset of customers using Databricks may have experienced failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Declarative Pipelines. Impact varied in severity and duration across the affected services during this window. Symptoms • Serverless SQL warehouses failed to start or experienced startup delays • Classic compute SQL warehouses failed to start or experienced intermittent delays • Declarative Pipelines experienced execution failures Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit a support ticket or contact [email protected]. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription