Is Databricks AWS down?

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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 • Databricks SQL availability was degraded during the incident window. 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.

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.

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

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.

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.

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

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.

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.

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.

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.

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