October 16, 2026 15:27 UTC 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. October 16, 2026 16:03 UTC 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, unavailable workspace UI features, or failures when starting or running workloads during this window. Symptoms • Genie One, the workspace app switcher, and other workspace UI features unavailable or returning errors • Serverless workloads, jobs, and SQL queries failing to start or returning errors • Notebooks and Databricks Apps failing to load or execute 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. October 16, 2026 16:36 UTC 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, unavailable workspace UI features, or failures when starting or running workloads during this window. Symptoms • Genie One, the workspace app switcher, and other workspace UI features are unavailable or returning errors • Serverless workloads, jobs, and SQL queries failing to start or returning errors • Notebooks and Databricks Apps failing to load or execute Current Status The issue has been mitigated, and service is operational. Next Update This is the final update for this incident. 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].
ES-2281237
Started October 12, 2026 at 5:42 PM UTC · 0m
IssuesMinor incident
resolved
October 12, 2026 12:57 UTC 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. October 12, 2026 13:15 UTC 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 pipelines. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on serverless compute 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. October 12, 2026 14:12 UTC 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 pipelines, SQL warehouses, and AI/BI dashboards and Genie. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start, or queries failing • AI/BI dashboards and Genie spaces failing to load or run queries Recommendations No customer action is required at this time. Current Status Our engineering teams are actively investigating elevated failures in Serverless compute allocation in this region. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. October 12, 2026 15:15 UTC 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 pipelines, SQL warehouses, and AI/BI dashboards and Genie. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start, or queries failing • AI/BI dashboards and Genie spaces failing to load or run queries Recommendations No customer action is required at this time. Current Status Our engineering teams are actively investigating elevated failures in Serverless compute allocation in this region. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. October 12, 2026 16:14 UTC 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 warehouses, and AI/BI dashboards, and Genie. Classic (non-serverless) compute is not affected. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS or ALLOCATION_TIMEOUT_NO_UNALLOCATED_CLUSTERS • Serverless job runs failing or timing out • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start • AI/BI dashboards and Genie spaces are unable to run queries Recommendations No customer action is required at this time. Current Status Our engineering teams have identified a potential issue with retrieving container images required to start Serverless compute in this region. We are actively working with our cloud provider to resolve it. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. October 12, 2026 16:45 UTC 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 encountered failures starting serverless workloads, cluster allocation timeouts, or failed and delayed job, pipeline, query, and dashboard operations during this window. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Serverless SQL warehouses are stuck in Starting, and queries, dashboards, or Genie requests are failing or timing out • Jobs and Declarative Pipelines run remaining pending, failing, or not progressing 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. October 12, 2026 17:42 UTC 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 encountered serverless workloads failing to start, cluster allocation timeouts, or failures in dependent jobs, pipelines, SQL warehouses, dashboards, and Genie experiences during this window. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Jobs and pipeline runs remaining pending, failing, or not progressing • Serverless SQL warehouses, AI/BI dashboards, and Genie spaces failing to start, load, or respond Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. 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].
ES-2263963
Started October 6, 2026 at 2:32 AM UTC · 0m
IssuesMinor incident
resolved
October 5, 2026 23:59 UTC 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, or dashboards that failed to load or refresh during this window. Symptoms • SQL queries failing or timing out • Dashboards failing to load, refresh, or showing empty or partial results • BI tool and SQL API connections timing out 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. October 6, 2026 02:32 UTC 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 dashboards that failed to load or refresh during this window. Symptoms • SQL statement execution failures or timeouts • AI/BI dashboards failing to load, refresh, or showing empty or partial results • BI tool connections and query requests timing out Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. 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]. October 6, 2026 02:32 UTC 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 that failed to load or refresh during this window. Symptoms • SQL statement execution failures or timeouts • AI/BI dashboards failing to load, refresh, or showing empty or partial results • BI tool connections and query requests timing out Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. 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].
ES-2248197
Started September 29, 2026 at 6:54 PM UTC · 0m
IssuesMinor incident
resolved
September 29, 2026 17:10 UTC 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. 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. September 29, 2026 17:43 UTC 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 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. September 29, 2026 17:55 UTC 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 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. September 29, 2026 18:54 UTC 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 during this window. Symptoms • Pipeline runs failing with control plane failure errors • Pipeline runs not progressing or not terminating as expected • Delayed or missing pipeline status information Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. 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].
ES-2231583
Started September 22, 2026 at 12:51 AM UTC · 0m
IssuesMinor incident
resolved
September 21, 2026 23:22 UTC 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. September 21, 2026 23:25 UTC 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 jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures and job run terminations during cluster startup • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue is under active investigation, with triage ongoing in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 21, 2026 23:48 UTC 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 termination failures, cluster allocation timeouts, and jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures; clusters stuck in Pending or Starting, and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 21, 2026 23:58 UTC 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 cluster launch failures, allocation timeouts, and failed or terminated workloads during this window. Symptoms • Classic compute cluster launch failures, with clusters stuck in Pending or Starting and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing 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. September 22, 2026 00:51 UTC 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 launch new compute, and jobs and pipeline runs may have failed, remained pending, or terminated unexpectedly during this window. Symptoms • Cluster launch failures, with clusters stuck in Pending or Starting, and notebook attach failures • Serverless workloads failing to start, with allocation timeouts or unexpected workload termination • Jobs and pipeline runs not starting on schedule, failing immediately, or not progressing Current Status The incident has been fully resolved, and service is operating normally. Next Update This is the final update for this incident. 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].
Regular Planned Maintenance
Started August 31, 2026 at 1:00 PM UTC · 0m
OutageMajor incident
resolved
August 21, 2026 19:33 UTC Scheduled - A maintenance event is scheduled to occur between 7:00 AM UTC and 1:00 PM UTC on Monday, August 31st, 2026. During this time window, running Lakebase endpoints will be restarted; clients may observe a downtime of a few seconds to reconnect; workloads may experience temporary performance degradation for approximately 10 minutes. Impacted services include: - Database connectivity may get interrupted. - Database transactions may be interrupted. We apologize for any inconvenience this may have caused. August 31, 2026 07:00 UTC Active - A maintenance event is scheduled to occur between 7:00 AM UTC and 1:00 PM UTC on Monday, August 31st, 2026. During this time window, running Lakebase endpoints will be restarted; clients may observe a downtime of a few seconds to reconnect; workloads may experience temporary performance degradation for approximately 10 minutes. Impacted services include: - Database connectivity may get interrupted. - Database transactions may be interrupted. We apologize for any inconvenience this may have caused. August 31, 2026 13:00 UTC Completed - Scheduled maintenance is complete.
ES-2154303
Started August 24, 2026 at 10:55 PM UTC · 0m
IssuesMinor incident
resolved
August 24, 2026 21:12 UTC 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. August 24, 2026 21:42 UTC 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 failures and failed connection attempts • Queries timing out or returning errors, and admin operations not completing • Applications backed by Lakebase returning errors Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress. Further updates will be provided as mitigation advances. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status. August 24, 2026 22:20 UTC 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 workloads during this window. Symptoms: • Failures when creating or accessing Lakebase databases • Connection failures, query timeouts, or errors on Lakebase-backed applications • Administrative operations not completing or remaining in progress Current Status: The issue has been mitigated and service is operational. Monitoring remains in place to confirm continued stability. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status. August 24, 2026 22:55 UTC 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 workloads during this window. Symptoms: • Database creation and administrative operations failing to complete • Connection failures or queries timing out against Lakebase databases • Applications backed by Lakebase returning errors Current Status: The issue has been resolved, and all affected services have been restored. Next Update: This is the final update for this incident.