GCP Databricks Outage History

GCP Databricks is up right now

GCP Databricks had 4 outages in the last 2 years totaling 9h 33m of downtime — averaging 0.2 incidents per month.

There were 4 GCP Databricks outages since May 5, 2026 totaling 9h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gcp.databricks.com

Minor September 29, 2026

ES-2248197

Detected by Pingoru
Sep 29, 2026, 05:12 PM UTC
Resolved
Sep 29, 2026, 06:55 PM UTC
Duration
1h 43m
Affected: LakeflowUnity Catalog (US-West1)
Timeline · 3 updates
  1. investigating Sep 29, 2026, 05:12 PM UTC

    Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Azure Databricks in West US 3 may experience failures or degraded availability with Declarative Pipelines. Affected customers may encounter pipeline runs that fail, do not start, or do not progress. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  2. identified Sep 29, 2026, 05:44 PM UTC

    Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Databricks may experience failures or degraded performance with Declarative Pipelines. Affected customers may find that pipeline runs fail intermittently or do not complete as expected. Symptoms • Pipeline runs failing with CONTROL_PLANE_FAILURE errors • Pipeline runs not progressing or terminating unexpectedly • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. monitoring Sep 29, 2026, 05:54 PM UTC

    Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded availability with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipelines that did not progress as expected during this window. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Delayed or missing pipeline status information Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Read the full incident report →

Minor July 10, 2026

ES-2052473

Detected by Pingoru
Jul 10, 2026, 11:38 PM UTC
Resolved
Jul 11, 2026, 12:40 AM UTC
Duration
1h 1m
Affected: ComputeLakeflowUnity Catalog (US-West1)Unity Catalog (Northamerica-Northeast1)Unity Catalog (Asia-South1)Unity Catalog (Australia-Southeast1)
Timeline · 1 update
  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.

Read the full incident report →

Minor May 26, 2026

ES-1940071

Detected by Pingoru
May 26, 2026, 07:39 PM UTC
Resolved
May 26, 2026, 10:14 PM UTC
Duration
2h 34m
Affected: LakeflowUnity Catalog (US-Central1)Unity Catalog (US-East1)Unity Catalog (US-East4)Unity Catalog (US-West4)Unity Catalog (Northamerica-Northeast1)Unity Catalog (EU-West1)Unity Catalog (EU-West2)Unity Catalog (Asia-Southeast1)Unity Catalog (Asia-South1)Unity Catalog (Australia-Southeast1)Unity Catalog (Southamerica-East1)
Timeline · 3 updates
  1. investigating May 26, 2026, 07:39 PM UTC

    We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  2. investigating May 26, 2026, 08:03 PM UTC

    Impact Summary Starting at 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. monitoring May 26, 2026, 09:11 PM UTC

    Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Read the full incident report →

Minor May 5, 2026

ES-1895876

Detected by Pingoru
May 05, 2026, 07:37 AM UTC
Resolved
May 05, 2026, 11:51 AM UTC
Duration
4h 13m
Affected: ComputeUnity Catalog (US-Central1)Unity Catalog (US-East1)Unity Catalog (US-East4)Unity Catalog (Northamerica-Northeast1)Unity Catalog (Australia-Southeast1)
Timeline · 3 updates

Read the full incident report →