Is Azure Databricks down?
Current Azure Databricks status is UP

We checked the official Azure Databricks Status Page 4 min. 24 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Azure Databricks Outages and Issues

Follow the recent outages and downtime for Azure Databricks in the table below.

Start Time

Type

Length

Message

Details

July 19, 2024 04:43 UTC

WARN

ongoing

Investigating issues in the Central US region

See more
Start Time

July 19, 2024 04:43 UTC

Type WARN
Affected Components

Central US - Automation

Central US - Azure AI Metrics Advisor

Central US - Azure AI Search

Central US - Azure AI Anomaly Detector

Central US - Azure AI Immersive Reader

Central US - Azure AI Vision

Central US - Content Moderator

Central US - Face API

Central US - Language Understanding (LUIS)

Central US - Azure AI Video Indexer

Central US - Azure Analysis Services

Central US - Azure Arc enabled data services

Central US - Azure Arc enabled Kubernetes

Central US - Azure Arc enabled servers

Central US - Azure Cache for Redis

Central US - Azure Chaos Studio

Central US - Azure Communications Gateway

Central US - Azure Container Apps

Central US - Azure Container Instances

Central US - Azure Container Registry

Central US - Azure Container Service

Central US - Azure Cosmos DB

Central US - Azure Data Explorer

Central US - Azure Data Factory

Central US - Azure Data Lake Storage Gen1

Central US - Azure Data Share

Central US - Azure Database for PostgreSQL

Central US - Azure Database for PostgreSQL flexible servers

Central US - Azure Database Migration Service

Central US - Azure Database Migration Service (classic)

Central US - Azure Databricks

Central US - Azure DDoS Protection

Central US - Azure Dev Spaces

Central US - Azure DevTest Labs

Central US - Azure Firewall

Central US - Azure Firewall Manager

Central US - Azure Functions

Central US - Azure HPC Cache

Central US - Azure IoT Central

Central US - Azure IoT Hub

Central US - IoT Hub Device Provisioning Service

Central US - Azure Key Vault Managed HSM

Central US - Azure Kubernetes Service (AKS)

Central US - Azure Machine Learning

Central US - Application Insights

Central US - AutoScale

Central US - Log Analytics

Central US - Azure Red Hat OpenShift

Central US - Azure Route Server

Central US - Azure Service Fabric

Central US - Azure SignalR Service

Central US - Azure Site Recovery

Central US - Azure Spring Cloud

Central US - Azure SQL Database

Central US - Azure Stream Analytics

Central US - Azure Synapse Analytics

Central US - Azure Time Series Insights

Central US - Azure Update Manager

Central US - Azure Virtual Network Manager

Central US - Azure VMware Solution

Central US - Azure Web PubSub

Central US - Cloud Services

Central US - Data Lake Analytics

Central US - Event Grid

Central US - Event Hubs

Central US - ExpressRoute Circuits

Central US - ExpressRoute Gateways

Central US - HDInsight

Central US - Microsoft Entra Domain Services

Central US - Network Infrastructure

Central US - Network Watcher

Central US - Notification Hubs

Central US - Scheduler

Central US - Service Bus

Central US - SQL Server Stretch Database

Central US - Storage Accounts

Central US - Virtual Machine Scale Sets

Central US - Virtual Machines

Central US - Virtual Network

Central US - Virtual WAN

Central US - VPN Gateway

Central US - Web Application Firewall

Non-Regional - Azure Virtual Desktop

Non-Regional - Azure Front Door

Non-Regional - Azure AI Translator

Non-Regional - Azure Managed Applications

Non-Regional - Universal Print

Non-Regional - Azure Migrate

Central US - Azure AI Speech

Central US - Azure File Sync

Central US - Application Gateway

Central US - Azure Backup

Central US - Azure Managed Instance for Apache Cassandra

Central US - Azure AI services

Central US - Azure Automanage

Central US - Azure NetApp Files

Central US - Azure Private Link

Central US - Azure AI Language

Central US - Media Services

Central US - Azure NAT Gateway

Central US - Batch

Central US - Key Vault

Central US - Load Balancer

Central US - Logic Apps

Central US - Microsoft Azure Attestation

Central US - API Management

Central US - App Configuration

Central US - App Service

Central US - App Service (Linux)

Central US - Web Apps Linux

Central US - Application Gateway for Containers

Message

Investigating issues in the Central US region

Details

Impact Statement: Starting at approximately 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services.
Current Status: We are aware of this issue and have engaged multiple teams. We’ve determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks. Mitigation has been confirmed for all Azure Storage clusters, the majority of services are now recovered. A small subset of services is still experiencing residual impact. Impacted customers will be continuing to communicate throuhg Azure service health portal. The next update will be provided in 60 minutes, or as events warrant.
https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region .
This message was last updated at 04:38 UTC on 19 July 2024

July 18, 2024 23:50 UTC

WARN

about 5 hours

Investigating issues in the Central US region

See more
Start Time

July 18, 2024 23:50 UTC

Type WARN
Affected Components

Central US - Azure Cache for Redis

Central US - Azure Data Explorer

Central US - Azure Data Factory

Central US - Azure Databricks

Message

Investigating issues in the Central US region

Details

Impact Statement: Starting at 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services.
Current Status: We are aware of this issue and have engaged multiple teams to investigate. As part of the investigation, we are reviewing previous deployments, and are running other workstreams to investigate for an underlying cause. The next update will be provided in 60 minutes, or as events warrant. 
Customers with disaster recovery procedures set up can consider taking steps to failover their services to another region https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region 
This message was last updated at 23:45 UTC on 18 July 2024

July 12, 2024 07:19 UTC

WARN

less than a minute

Mitigated - Managed Identity - Australia East, Australia Southeast

See more
Start Time

July 12, 2024 07:19 UTC

Type WARN
Affected Components

Australia East - Azure Virtual Desktop

Australia East - Virtual Machines

Australia Southeast - Virtual Machines

Australia East - Azure Databricks

Australia Southeast - Azure Databricks

Australia Southeast - Azure Virtual Desktop

Australia East - Virtual Machine Scale Sets

Australia Southeast - Virtual Machine Scale Sets

Non-Regional - Azure Virtual Desktop

Message

Mitigated - Managed Identity - Australia East, Australia Southeast

Details

What happened?
Between at 00:55 UTC on 12 Jul 2024 and 06:28 UTC on 12 Jul 2024, you have been identified among a subset of customers using Managed Service Identity (MSI) for Azure resources who may experience failures when requesting tokens for managed identities associated with Virtual Machines or Virtual Machine Scale Sets, Windows Virtual Desktop, Azure Databricks and any other Azure service that relies on MSI.
 What do we know so far?
We identified that a configuration change introduced in a recent deployment had caused this issue. We had to roll back the new change and restart to the last known good build.
How did we respond?
 What happens next?
This message was last updated at 07:15 UTC on 12 July 2024

July 12, 2024 07:19 UTC

WARN

9 minutes

Mitigated - Managed Identity - Australia East, Australia Southeast

See more
Start Time

July 12, 2024 07:19 UTC

Type WARN
Affected Components

Australia East - Azure Virtual Desktop

Australia East - Virtual Machines

Australia Southeast - Virtual Machines

Australia East - Azure Databricks

Australia Southeast - Azure Databricks

Australia Southeast - Azure Virtual Desktop

Australia East - Virtual Machine Scale Sets

Australia Southeast - Virtual Machine Scale Sets

Non-Regional - Azure Virtual Desktop

Message

Mitigated - Managed Identity - Australia East, Australia Southeast

Details

What happened?
Between at 00:55 UTC on 12 Jul 2024 and 06:28 UTC on 12 Jul 2024, you have been identified among a subset of customers using Managed Service Identity (MSI) for Azure resources who may experience failures when requesting tokens for managed identities associated with Virtual Machines or Virtual Machine Scale Sets, Windows Virtual Desktop, Azure Databricks and any other Azure service that relies on MSI.
 What do we know so far?
We identified that a configuration change introduced in a recent deployment had caused this issue. We had to roll back the new change and restart to the last known good build.
How did we respond?
 What happens next?
This message was last updated at 07:15 UTC on 12 July 2024

July 12, 2024 05:33 UTC

DOWN

about 2 hours

Active - Managed Identity - Applying Mitigation - Australia East, Australia Southeast

See more
Start Time

July 12, 2024 05:33 UTC

Type DOWN
Affected Components

Australia Southeast - Virtual Machines

Australia Southeast - Azure Databricks

Australia Southeast - Virtual Machine Scale Sets

Message

Active - Managed Identity - Applying Mitigation - Australia East, Australia Southeast

Details

Impact Statement: Starting at 00:55 UTC on 12 Jul 2024, you have been identified among a subset of customers in Australia East and Australia Southeast using Managed Service Identity (MSI) for Azure resources who may experience failures when requesting tokens for managed identities associated with Virtual Machines or Virtual Machine Scale Sets, Windows Virtual Desktop, Azure Databricks and any other Azure service that relies on MSI. We determined that a configuration change introduced in a recent deployment had caused this issue.
Current Status: We are pursuing multiple parallel workstreams for mitigation including rolling back to the previous configuration and adding more resources. The next update will be provided in 60 minutes, or as events warrant
This message was last updated at 05:30 UTC on 12 July 2024

2024-07-19 05:05:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 05:05:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 05:05:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 05:05:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 05:05:27 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Azure Databricks History

StatusGator has over 9 years of Azure Databricks status history.

2 status changes in the last 24 hours

Azure Databricks status, last 24 hours:

6:00 AM
12:00 PM
6:00 PM
12:00 AM
6:00 AM
6:00 AM
6:00 PM
6:00 AM
  • Up: 19 hours

  • Warn: 5 hours

  • Down: 0 minutes

Azure Databricks Outage and Status History

We've been monitoring Azure Databricks outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Databricks Status Page:

Instant enriched data from
3,970 status pages

About Our Azure Databricks Status Page Integration

Azure Databricks is a Cloud Infrastructure and Microsoft solution that StatusGator has been monitoring since March 2015. Over the past over 9 years, we have collected data on on more than 1,804 outages that affected Azure Databricks users. When Azure Databricks publishes downtime on their status page, they do so across 5,887 components and 65 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 2,400 StatusGator users monitor Azure Databricks to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 169,900 notifications to our users about Azure Databricks incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Azure Databricks is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Azure Databricks is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Azure Databricks does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need Azure Databricks maintenance notifications, please email us.

Azure Databricks does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Azure Databricks maintenance events into your unified calendar.

When Azure Databricks posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Azure Databricks has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Azure Databricks has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Azure Databricks Down?

Are you experiencing issues with Azure Databricks? Sign up to receive notifications when Azure Databricks publishes outages.

Azure Databricks Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,970 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Azure Databricks?

Sign up for StatusGator and see all historical information about Azure Databricks outages and performance issues. Get free, instant notifications when Azure Databricks goes down.

No outages or status changes in the last 24 hours

Azure Databricks status, last 24 hours:

8:00 PM
2:00 AM
8:00 AM
2:00 PM
8:00 PM
8:00 PM
8:00 AM
8:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Azure Databricks Outage and Status History

We've been monitoring Azure Databricks outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Databricks Status Page: