Databricks AWS experienced a minor incident on July 30, 2026 affecting Compute and Databricks SQL and 1 more component, lasting 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jul 30, 2026, 01:57 AM UTC
Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs and Declarative Pipelines. The disruption has since been mitigated and normal availability was restored. Symptoms • Serverless clusters failed to launch, returning cluster-matching errors • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability • Databricks SQL availability was degraded during the incident window. 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 Jul 30, 2026, 01:57 AM UTC
Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs and Declarative Pipelines. The disruption has since been mitigated and normal availability was restored. Symptoms • Serverless clusters failed to launch, returning cluster-matching errors • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability 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 Jul 30, 2026, 02:30 AM UTC
Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Databricks SQL, Jobs, and Declarative Pipelines. Normal availability was restored by the end of the impact window. Symptoms • Serverless compute clusters failed to launch, returning cluster-matching errors. • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability. • Databricks SQL availability was degraded during the incident window. 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