Databricks
Infrastructure. Source: Databricks status page.
History starts 2026-08-24 21:12 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 6+
- Median to mitigation
- 40m
- Median to resolution
- 1h 44m
- p95 to resolution
- 4h 45m
- Naming an upstream provider
- 83%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 3 |
| A provider or third-party service this vendor depends on failed | 2 |
| Orchestration, control plane, service discovery or load balancing failed | 1 |
Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
ES-2292938
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
We are actively investigating an issue with the Databricks service. We will provide another update within 1 hour, or sooner if there is a material change in service status.
-
monitoring
Impact Summary Between 15:07 UTC and 15:49 UTC on October 16, 2026, customers using Databricks may have experienced degraded availability with Serverless Compute, Databricks Apps, Databricks SQL, Jobs, Notebooks, and Genie One. Affected customers may have encountered errors,...
-
resolved
Impact Summary Between 15:07 UTC and 15:49 UTC on October 16, 2026, customers using Databricks may have experienced degraded availability with Serverless Compute, Databricks Apps, Databricks SQL, Jobs, Notebooks, and Genie One. Affected customers may have encountered errors,...
Excerpts are shortened. Read the full incident on Databricks's status page.
ES-2281237
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
Names an upstream provider: AWS.
-
investigating
We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.
-
investigating
Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run serverless workloads for notebooks, jobs, and Lakeflow...
-
investigating
Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including notebooks, jobs, Lakeflow...
-
investigating
Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including notebooks, jobs, Lakeflow...
-
identified
Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including jobs, Lakeflow pipelines, SQL...
-
monitoring
Impact Summary Between 12:30 UTC and 16:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Genie. Affected customers may have...
-
resolved
Impact Summary Between 12:30 UTC and 16:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Genie. Affected customers may have...
Excerpts are shortened. Read the full incident on Databricks's status page.
ES-2263963
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
Names an upstream provider: AWS.
-
monitoring
Impact Summary Between 23:10 UTC and 23:31 UTC on October 05, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded performance with Databricks SQL and AI/BI. Affected customers may have encountered SQL statement execution failures, query timeouts,...
-
monitoring
Impact Summary Between 23:10 UTC and 23:31 UTC on October 05, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded performance with Databricks SQL and AI/BI. Affected customers may have encountered SQL query failures or timeouts, and AI/BI...
-
resolved
Impact Summary Between 23:10 UTC and 23:31 UTC October 05, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded performance with Databricks SQL and AI/BI. Affected customers may have encountered SQL query failures or timeouts, and AI/BI dashboards...
Excerpts are shortened. Read the full incident on Databricks's status page.
ES-2248197
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
Names an upstream provider: Azure.
-
investigating
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....
-
identified
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...
-
monitoring
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...
-
resolved
Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded performance with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipeline runs that did not progress...
Excerpts are shortened. Read the full incident on Databricks's status page.
ES-2231583
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
Names an upstream provider: AWS.
-
investigating
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
Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may experience degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, operation timeouts, and...
-
identified
Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may be experiencing a complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may encounter compute launch and...
-
monitoring
Impact Summary Between 22:57 UTC and 23:45 UTC on September 21, 2026, customers using Databricks on AWS in US East 1 may have experienced complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered...
-
resolved
Impact Summary Between 22:57 UTC and 23:45 UTC on September 21, 2026, customers using Databricks on AWS in US East 1 may have experienced complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have been unable to...
Excerpts are shortened. Read the full incident on Databricks's status page.
ES-2154303
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Names an upstream provider: AWS.
-
investigating
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.
-
identified
Starting at 20:22 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may experience degraded availability with Lakebase. Affected customers may be unable to create, access, or operate Lakebase databases and related workloads. Symptoms: • Database creation...
-
monitoring
Impact Summary: Between 20:22 UTC and 22:08 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related...
-
resolved
Impact Summary: Between 20:22 UTC and 22:08 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related...
Excerpts are shortened. Read the full incident on Databricks's status page.