Databricks AWS Outage History

Started Oct 16, 2026, 03:27 PM UTC· resolved Oct 16, 2026, 04:36 PM UTC

1. investigating Oct 16, 2026, 03:27 PM UTC

   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.

2. monitoring Oct 16, 2026, 04:03 PM UTC

   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.

3. resolved Oct 16, 2026, 04:36 PM UTC

   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].

Read the full incident report →

Started Oct 12, 2026, 12:57 PM UTC· resolved Oct 12, 2026, 05:42 PM UTC

1. investigating Oct 12, 2026, 12:57 PM UTC

   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.

2. investigating Oct 12, 2026, 01:15 PM UTC

   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.

3. investigating Oct 12, 2026, 02:12 PM UTC

   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.

4. investigating Oct 12, 2026, 03:15 PM UTC

   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.

5. identified Oct 12, 2026, 04:14 PM UTC

   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.

6. monitoring Oct 12, 2026, 04:45 PM UTC

   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.

7. resolved Oct 12, 2026, 05:42 PM UTC

   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].

Read the full incident report →

Started Oct 05, 2026, 11:59 PM UTC· resolved Oct 06, 2026, 02:32 AM UTC

1. monitoring Oct 05, 2026, 11:59 PM UTC

   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.

2. monitoring Oct 06, 2026, 02:32 AM UTC

   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].

3. resolved Oct 06, 2026, 02:32 AM UTC

   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].

Read the full incident report →

Started Sep 29, 2026, 05:10 PM UTC· resolved Sep 29, 2026, 06:54 PM UTC

1. investigating Sep 29, 2026, 05:10 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:43 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:55 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.

4. resolved Sep 29, 2026, 06: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 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]. 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

Read the full incident report →

Started Sep 21, 2026, 11:22 PM UTC· resolved Sep 22, 2026, 12:51 AM UTC

1. investigating Sep 21, 2026, 11:22 PM UTC

   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.

2. investigating Sep 21, 2026, 11:25 PM UTC

   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.

3. identified Sep 21, 2026, 11:48 PM UTC

   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.

4. monitoring Sep 21, 2026, 11:58 PM UTC

   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.

5. resolved Sep 22, 2026, 12:51 AM UTC

   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]. 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

Read the full incident report →

Started Aug 24, 2026, 09:12 PM UTC· resolved Aug 24, 2026, 10:55 PM UTC

1. investigating Aug 24, 2026, 09:12 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. identified Aug 24, 2026, 09:42 PM UTC

   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.

3. monitoring Aug 24, 2026, 10:20 PM UTC

   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.

4. resolved Aug 24, 2026, 10:55 PM UTC

   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. 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

Read the full incident report →

Started Aug 06, 2026, 10:55 AM UTC· resolved Aug 06, 2026, 02:04 PM UTC

1. investigating Aug 06, 2026, 10:55 AM UTC

   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.

2. investigating Aug 06, 2026, 11:06 AM UTC

   Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute resources, including SQL warehouses. Symptoms • Serverless SQL warehouses failing to start • Classic compute SQL warehouses failing to start • Delays or errors during compute cluster startup Recommendations No customer action is required at this time. Current Status The incident is under active investigation as the team works to identify the root cause of Serverless Compute startup failures. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. investigating Aug 06, 2026, 12:02 PM UTC

   Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Lakeflow Declarative Pipelines. Symptoms • Serverless SQL warehouses failing to start • Classic compute SQL warehouses failing to start or experiencing intermittent delays • Lakeflow Declarative Pipelines failing Recommendations No customer action is required at this time. Current Status The incident remains under active investigation, with engineering teams working to identify the root cause and mitigate capacity-related startup failures affecting Serverless Compute, Classic Compute, and Lakeflow Declarative Pipelines. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Aug 06, 2026, 12:54 PM UTC

   Starting at approximately 10:10 UTC on August 6, 2026, customers using Databricks may be experiencing failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Lakeflow Declarative Pipelines. Symptoms • Serverless SQL warehouses failing to start • Classic compute SQL warehouses failing to start or experiencing intermittent delays • Lakeflow Declarative Pipelines failing Recommendations No customer action is required at this time. Current Status The root cause has been identified as a capacity issue that caused some system components to run out of available memory and to restart repeatedly. Engineering continues active mitigation while monitoring for intermittent errors recurring across affected services. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Aug 06, 2026, 01:21 PM UTC

   Between 10:10 UTC and 13:00 UTC on August 6, 2026, a subset of customers using Databricks may have experienced failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Declarative Pipelines. Impact varied in severity and duration across the affected services during this window. Symptoms • Serverless SQL warehouses failed to start or experienced startup delays • Classic compute SQL warehouses failed to start or experienced intermittent delays • Declarative Pipelines experienced execution failures 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.

6. resolved Aug 06, 2026, 02:04 PM UTC

   Between 10:10 UTC and 13:00 UTC on August 6, 2026, a subset of customers using Databricks may have experienced failures or delays when starting Serverless Compute and Classic Compute resources, including SQL warehouses, as well as failures affecting Declarative Pipelines. Impact varied in severity and duration across the affected services during this window. Symptoms • Serverless SQL warehouses failed to start or experienced startup delays • Classic compute SQL warehouses failed to start or experienced intermittent delays • Declarative Pipelines experienced execution failures 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

Read the full incident report →

Started Jul 30, 2026, 01:57 AM UTC· resolved Jul 30, 2026, 02:30 AM UTC

1. monitoring Jul 30, 2026, 01:57 AM UTC

   Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs and Declarative Pipelines. The disruption has since been mitigated and normal availability was restored. Symptoms • Serverless clusters failed to launch, returning cluster-matching errors • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability 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.

2. resolved Jul 30, 2026, 02:30 AM UTC

   Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Databricks SQL, Jobs, and Declarative Pipelines. Normal availability was restored by the end of the impact window. Symptoms • Serverless compute clusters failed to launch, returning cluster-matching errors. • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability. • Databricks SQL availability was degraded during the incident window. 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

Read the full incident report →

Started Jul 10, 2026, 11:36 PM UTC· resolved Jul 11, 2026, 12:36 AM UTC

1. 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.

2. 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

Read the full incident report →

Started Jul 06, 2026, 02:51 PM UTC· resolved Jul 06, 2026, 04:25 PM UTC

1. identified Jul 06, 2026, 02:51 PM UTC

   Starting at approximately 09:55 UTC on July 6, 2026, customers using Databricks may be experiencing failures or unexpected terminations when launching or running compute clusters, as well as failures with job runs on affected services. A subset of customers may be experiencing degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminating shortly after launch • New cluster launches failing to start • Job runs failing or terminating unexpectedly • Degraded UI page loads Recommendations No customer action is required at this time. Current Status The root cause has been identified as a cloud provider issue impacting Classic Compute and Jobs, and the team is monitoring as affected services show signs of recovery. For more details, refer to https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_5269E_F1B7AF74706 Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. monitoring Jul 06, 2026, 03:36 PM UTC

   Between 09:55 UTC and 13:54 UTC on July 6, 2026, a subset of customers using Databricks may have experienced failures or unexpected terminations when launching or running compute clusters, as well as failures with job runs on affected services. A subset of customers may have experienced degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminated shortly after launch • New cluster launches failed to start • Job runs failed or terminated unexpectedly • Degraded UI page loads Current Status The issue has been mitigated and services have been restored. For more details, refer to https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_5269E_F1B7AF74706 Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. resolved Jul 06, 2026, 04:25 PM UTC

   Between 09:55 UTC and 13:54 UTC on July 6, 2026, a subset of customers using Databricks may have experienced failures or unexpected terminations when launching or running compute clusters, as well as failures with job runs on affected services. A subset of customers may have experienced degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminated shortly after launch • New cluster launches failed to start • Job runs failed or terminated unexpectedly • Degraded UI page loads 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

Read the full incident report →

Started Jun 29, 2026, 10:17 PM UTC· resolved Jun 29, 2026, 11:52 PM UTC

1. investigating Jun 29, 2026, 10:17 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. monitoring Jun 29, 2026, 10:52 PM UTC

   Impact Summary From 29 June 2026 21:22 UTC to 29 June 2026 22:19 UTC, customers using Databricks Apps in AWS US East (N. Virginia) may have been unable to create, deploy, stop, or delete apps. Service has been restored. Symptoms Customers may have experienced: - App creation, deployment, stop, and deletion operations failing or returning errors - App management operations not completing through the Workspace UI or Databricks APIs Recommendations No customer action is required. Current Status Service has been restored as of 29 June 2026 22:19 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. resolved Jun 29, 2026, 11:52 PM UTC

   Impact Summary Between 29 June 2026 21:22 UTC and 29 June 2026 22:19 UTC, customers using Databricks Apps in AWS US East (N. Virginia) may have been unable to create, deploy, stop, or delete apps. Symptoms Customers may have experienced: - App creation, deployment, stop, and deletion operations failing or returning errors - App management operations not completing through the Workspace UI or Databricks APIs Current Status This incident has been fully resolved as of 29 June 2026 22:19 UTC. We apologize for the disruption. 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

Read the full incident report →

Started Jun 08, 2026, 04:37 PM UTC· resolved Jun 08, 2026, 07:08 PM UTC

1. investigating Jun 08, 2026, 04:37 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. monitoring Jun 08, 2026, 05:12 PM UTC

   Impact Summary From 2026-06-08 15:55 UTC to 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Service has been restored. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Recommendations No customer action is required. Current Status Service has been restored as of 2026-06-08 16:35 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

3. resolved Jun 08, 2026, 07:08 PM UTC

   Impact Summary Between 2026-06-08 15:55 UTC and 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Current Status This incident has been fully resolved as of 2026-06-08 16:35 UTC, and Unity Catalog is operating normally. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 31, 2026, 02:02 AM UTC· resolved May 31, 2026, 08:16 AM UTC

1. investigating May 31, 2026, 02:02 AM 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 31, 2026, 02:36 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing failures and errors with Declarative Pipelines and Lakebase, and our engineering teams are working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified May 31, 2026, 03:20 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified May 31, 2026, 04:34 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified May 31, 2026, 05:39 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified May 31, 2026, 06:36 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. identified May 31, 2026, 07:18 AM UTC

   Starting at approximately 00:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

8. monitoring May 31, 2026, 07:35 AM UTC

   Between 00:00 UTC and 07:27 UTC on May 31, 2026, customers using Databricks may have experienced errors and failures with Declarative Pipelines and Lakebase. A subset of customers may have been unable to run or complete pipeline workloads, and may have experienced failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs failed or terminated unexpectedly with errors, including synced table pipeline failures • Lakebase queries and connections failed with 'Couldn't connect to compute node' errors • Synced table pipelines were unable to complete successfully Current Status The issue has been mitigated and services have 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.

9. resolved May 31, 2026, 08:16 AM UTC

   Between 00:00 UTC and 07:27 UTC on May 31, 2026, customers using Databricks may have experienced errors and failures with Declarative Pipelines and Lakebase. A subset of customers may have been unable to run or complete pipeline workloads, and may have experienced failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs failed or terminated unexpectedly with errors, including synced table pipeline failures • Lakebase queries and connections failed with connectivity errors • Synced table pipelines were unable to complete successfully 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

Read the full incident report →

Started May 26, 2026, 07:01 PM UTC· resolved May 26, 2026, 10:12 PM UTC

1. investigating May 26, 2026, 07:01 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:04 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:10 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.

4. resolved May 26, 2026, 10:12 PM UTC

   Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Current Status This incident has been fully resolved and normal operation has been restored. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 19, 2026, 12:53 AM UTC· resolved May 19, 2026, 04:43 AM UTC

1. investigating May 19, 2026, 12:53 AM UTC

   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.

2. investigating May 19, 2026, 01:23 AM UTC

   Starting at approximately 00:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute workloads. Affected customers may observe errors or inability to start or run Serverless Compute jobs. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing jobs and pipelines from running • Errors when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Our engineering teams are actively investigating the issue. Current Status We are actively investigating a disruption affecting Serverless Compute and will provide updates as more information 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 19, 2026, 01:52 AM UTC

   Between 00:34 UTC and 01:40 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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.

4. identified May 19, 2026, 02:19 AM UTC

   Starting at approximately 00:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC on May 19, 2026, during which services appeared to stabilize before a further period of disruption was observed. Affected customers may be encountering errors, cluster allocation timeouts, or unexpected termination of workloads. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing Declarative Pipelines and Jobs from running • Errors returned when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Current Status The issue has been identified and engineering teams are applying mitigations. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring May 19, 2026, 03:22 AM UTC

   Between 00:34 UTC and 03:00 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC during which services appeared to stabilize before further periods of disruption were observed. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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.

6. resolved May 19, 2026, 04:43 AM UTC

   Between 00:34 UTC and 03:00 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC during which services appeared to stabilize before further periods of disruption were observed. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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

Read the full incident report →

Started May 14, 2026, 06:04 AM UTC· resolved May 14, 2026, 08:57 AM UTC

1. investigating May 14, 2026, 06:04 AM 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 14, 2026, 06:38 AM UTC

   Impact Summary Starting at 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: - Errors when opening notebooks or browsing workspace folders - Failures when starting clusters or running jobs - Errors loading Databricks SQL queries and AI/BI Dashboards - Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We are actively investigating and working to restore normal service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified May 14, 2026, 07:20 AM UTC

   Impact Summary Starting at 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We have identified the cause of the issue and are working to apply a mitigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. monitoring May 14, 2026, 08:02 AM UTC

   Impact Summary Between 05:17 UTC and 07:43 UTC on 14 May 2026, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may have been unable to complete operations across these services. Symptoms Customers may have observed: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status A mitigation has been applied and we are monitoring the services for full recovery. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. resolved May 14, 2026, 08:57 AM UTC

   Impact Summary Between 14 May 2026 05:17 UTC and 14 May 2026 07:43 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 experienced failures completing operations across these services. Symptoms Customers experienced: - Errors when opening notebooks or browsing workspace folders - Failures when starting clusters or running jobs - Errors loading Databricks SQL queries and AI/BI Dashboards - Failures when calling Databricks APIs Current Status This incident has been fully resolved as of 14 May 2026 07:43 UTC. Normal operation has been restored. We apologize for the disruption. 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

Read the full incident report →

Started May 08, 2026, 12:20 AM UTC· resolved May 09, 2026, 02:32 AM UTC

1. investigating May 08, 2026, 12:20 AM 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 08, 2026, 12:47 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability. Symptoms Customers may observe: - General unavailability of Databricks services, including - Unity Catalog operations failing or not completing - Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations No customer action is required at this time. Current Status Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1. We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified May 08, 2026, 01:09 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability. Symptoms Customers may observe: - General unavailability of Databricks services, including - Unity Catalog operations failing or not completing - Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations No customer action is required at this time. Current Status Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1. We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified May 08, 2026, 02:32 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability. Symptoms Customers may observe: - General unavailability of Databricks services, including - Unity Catalog operations failing or not completing - Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations No customer action is required at this time. Current Status Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1. We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified May 08, 2026, 02:48 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures. Symptoms Customers may observe: - General unavailability of Databricks services, including - Unity Catalog operations failing or not completing - Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts. - https://docs.databricks.com/aws/en/compute/flexible-node-types - https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools Current Status Our engineering team has moved most services out of the impacted AZ. While many services are returning to service, customers may still see increased latency or intermittent job failures while the region continues to stabilize. We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information.

6. identified May 08, 2026, 04:17 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures. Symptoms Customers may observe: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts. * Flexible Node Types: https://docs.databricks.com/aws/en/compute/flexible-node-types * Auto-AZ with Pools: https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools Current Status We have identified the cause of this incident. Our engineering team has moved most services out of the impacted availability zone. While many services are returning to normal operation, customers may still experience increased latency or intermittent failures while the region continues to stabilize. We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.

7. identified May 08, 2026, 06:10 AM UTC

   Impact Summary Starting at 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures. Symptoms Customers may observe: General unavailability of Databricks services Unity Catalog operations failing or not completing Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures Recommendations Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts. Flexible Node Types: https://docs.databricks.com/aws/en/compute/flexible-node-types Auto-AZ with Pools: https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools Current Status Our engineering team has moved most services out of the impacted availability zone. While many services are returning to normal operation, customers may still experience increased latency or intermittent failures while the region continues to stabilize. We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

8. monitoring May 08, 2026, 07:32 AM UTC

   Impact Summary From 07 May 2026 23:59 UTC to 08 May 2026 06:00 UTC, customers using Databricks services in AWS us-east-1 experienced degraded service or failures. Service has been restored. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Recommendations No customer action is required at this time. Current Status Service has been restored as of 08 May 2026 06:00 UTC. Our engineering team is actively monitoring to confirm full stabilization across all affected services. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

9. monitoring May 08, 2026, 06:03 PM UTC

   Impact Summary Starting 07 May 2026 23:59 UTC customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Recommendations No customer action is required at this time. Current Status Databricks services have been restored as of 08 May 2026 06:00 UTC. Some additional degradation was observed from 17:03 UTC to 17:24 UTC. Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

10. monitoring May 08, 2026, 08:03 PM UTC

    Impact Summary Starting 07 May 2026 23:59 UTC customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Recommendations No customer action is required at this time. Current Status Databricks services have been restored as of 08 May 2026 06:00 UTC. Some additional degradation was observed from 17:03 UTC to 17:24 UTC. Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

11. monitoring May 08, 2026, 10:03 PM UTC

    Impact Summary Starting 07 May 2026 23:59 UTC customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Recommendations No customer action is required at this time. Current Status Databricks services have been restored as of 08 May 2026 06:00 UTC. Some additional degradation was observed from 17:03 UTC to 17:24 UTC. Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

12. monitoring May 09, 2026, 12:30 AM UTC

    Impact Summary From 07 May 2026 23:59 UTC to 08 May 2026 17:24 UTC, and again from 23:36 UTC to 23:55 UTC, customers using Databricks workspaces in the AWS us-east-1 region experienced intermittent errors and failures across catalog, compute, and job execution features. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Current Status Databricks services have been restored as of 08 May 2026 06:00 UTC. Some additional degradation was observed from 17:03 UTC to 17:24 UTC and from 23:36 UTC to 23:55 UTC. Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

13. resolved May 09, 2026, 02:32 AM UTC

    Impact Summary From 07 May 2026 23:59 UTC to 08 May 2026 17:24 UTC, and again from 23:36 UTC to 23:55 UTC, customers using Databricks workspaces in the AWS us-east-1 region experienced intermittent errors and failures across catalog, compute, and job execution features. Symptoms Customers experienced: * General unavailability of Databricks services * Unity Catalog operations failing or not completing * Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures * Mosaic AI Vector Search queries failing or experiencing degraded availability * Intermittent issues with authentication and login Current Status Databricks services have been restored as of 08 May 2026 06:00 UTC. Some additional degradation was observed from 17:03 UTC to 17:24 UTC and from 23:36 UTC to 23:55 UTC. This incident has been fully resolved as of 08 May 2026 23:55 UTC. Normal operation has been restored. This incident was related to a cloud provider issue. Additional information is available on the cloud provider's status page: https://health.aws.com/health/status. If you require further details about this incident, please submit a support ticket or contact [email protected]. We apologize for the disruption. For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 05, 2026, 07:40 AM UTC· resolved May 05, 2026, 11:44 AM UTC

1. identified May 05, 2026, 07:40 AM UTC

   Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 05:55 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified May 05, 2026, 09:22 AM UTC

   Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 08:06 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. monitoring May 05, 2026, 10:56 AM UTC

   Impact Summary Between 03:33 UTC and 08:06 UTC on 05 May 2026 , Classic Compute in multiple regions may have failed to start clusters when init scripts configured. There was brief recovery observed at 05:55 UTC. Full recovery was observed at 08:06 UTC. Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status The issue has been mitigated. We are continuing to monitor for any residual impact. 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 →