Databricks Azure Outage History

Databricks Azure is up right now

There were 3 Databricks Azure outages since April 27, 2026 totaling 11h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.azuredatabricks.net

Minor May 3, 2026

ES-1893276

Detected by Pingoru
May 03, 2026, 10:19 AM UTC
Resolved
May 03, 2026, 01:13 PM UTC
Duration
2h 54m
Affected: LakebaseUnity Catalog (West Europe)
Timeline · 2 updates
  1. investigating May 03, 2026, 10:19 AM UTC

    We are actively investigating an issue with the Databricks service - Lakebase, some Projects may experience delays in starting up. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  2. monitoring May 03, 2026, 10:42 AM UTC

    Impact Summary Between 09:36 UTC and 10:16 UTC on 03 May 2026, customers using Lakebase may have experienced delays in some Projects starting up. Current Status Service has been restored as of 03 May 2026 10:16 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.

Read the full incident report →

Minor April 28, 2026

ES-1885183

Detected by Pingoru
Apr 28, 2026, 05:47 PM UTC
Resolved
Apr 28, 2026, 07:43 PM UTC
Duration
1h 56m
Affected: LakeflowNotebooks (US Gov Virginia)
Timeline · 3 updates
  1. investigating Apr 28, 2026, 05:47 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 Apr 28, 2026, 06:15 PM UTC

    Impact Summary Starting at 28 April 2026 17:21 UTC, Lakeflow Jobs and Lakeflow Spark Declarative Pipelines in Azure Government may fail to start or execute. Symptoms Customers may observe: - Job runs failing to start or remaining in a pending state - Pipeline updates failing to trigger or execute - Active workloads experiencing unexpected interruptions Recommendations No customer action is required at this time. Current Status Databricks engineering is investigating the issue. We will provide further updates as the investigation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. monitoring Apr 28, 2026, 06:30 PM UTC

    Impact Summary Between 28 April 2026 17:21 UTC and 28 April 2026 18:22 UTC, Lakeflow Jobs and Lakeflow Spark Declarative Pipelines in Azure Government experienced disruptions. Service has been restored. Symptoms Customers may have observed: - Job runs failing to start or remaining in a pending state - Pipeline updates failing to trigger or execute - Active workloads experiencing unexpected interruptions Recommendations No customer action is required at this time. Current Status Service was restored as of 28 April 2026 18:22 UTC. Databricks engineering is 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.

Read the full incident report →

Minor April 27, 2026

ES-1852958

Detected by Pingoru
Apr 27, 2026, 08:03 PM UTC
Resolved
Apr 28, 2026, 02:43 AM UTC
Duration
6h 39m
Affected: ComputeLakeflowUnity Catalog (East US 2)
Timeline · 5 updates
  1. investigating Apr 27, 2026, 08:03 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. identified Apr 27, 2026, 08:22 PM UTC

    Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute resources in Azure East US 2 may experience degraded performance. Symptoms Customers may observe: - Serverless workloads taking longer than expected to start or complete - Intermittent failures or timeouts on Serverless Compute jobs and queries - Slower response times for notebooks and pipelines using Serverless Compute Recommendations No customer action is required at this time. Current Status We have identified the root cause of this issue and are actively working with our cloud provider on remediation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. identified Apr 27, 2026, 09:06 PM UTC

    Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute in Azure East US 2 may experience failures or become unavailable. Symptoms Customers may observe: - Serverless workloads failing to start or execute - Serverless compute requests returning errors or timing out Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident and are actively working to restore service. We will continue to provide updates as remediation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  4. identified Apr 27, 2026, 10:15 PM UTC

    Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute in Azure East US 2 may experience failures or become unavailable. Symptoms Customers may observe: - Serverless workloads failing to start or execute - Serverless compute requests returning errors or timing out Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident and are actively working to restore service. We will continue to provide updates as remediation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  5. monitoring Apr 27, 2026, 11:15 PM UTC

    Impact Summary Between 27 April 2026 18:43 UTC and 27 April 2026 23:02 UTC, Serverless Compute resources in Azure East US 2 experienced degraded performance. Symptoms Customers may have observed: - Serverless workloads taking longer than expected to start or complete - Intermittent failures or timeouts on Serverless Compute jobs and queries - Slower response times for Lakeflow Jobs and pipelines using Serverless Compute Recommendations No customer action is required at this time. Current Status Full mitigation was confirmed at 27 April 2026 23:02 UTC. Service has been restored and 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.

Read the full incident report →

Looking to track Databricks Azure downtime and outages?

Pingoru polls Databricks Azure's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Databricks Azure reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Databricks Azure alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Databricks Azure for free

5 free monitors · No credit card required