GCP Databricks incident

ES-2052473

Minor Resolved View vendor source →

GCP Databricks experienced a minor incident on July 10, 2026 affecting Compute and Lakeflow and 1 more component, lasting 1h 1m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 11:38 PM UTC
Resolved
Jul 11, 2026, 12:40 AM UTC
Duration
1h 1m
Detected by Pingoru
Jul 10, 2026, 11:38 PM UTC

Affected components

ComputeLakeflowUnity Catalog (US-West1)Unity Catalog (Northamerica-Northeast1)Unity Catalog (Asia-South1)Unity Catalog (Australia-Southeast1)

Update timeline

  1. monitoring Jul 10, 2026, 11:38 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.