Databricks AWS experienced a minor incident on July 10, 2026 affecting Compute and Lakeflow and 1 more component, lasting 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jul 10, 2026, 11:36 PM UTC
Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load 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 10, 2026, 11:36 PM UTC
Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load 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 11, 2026, 12:36 AM UTC
Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue was resolved and normal service was restored by the end of the impact window. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Some workspace console pages failed to load, showing errors related to cluster configuration or startup 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