Check if Azure Databricks is down, recent outages, user-reported issues, and outages map.
Azure Databricks is working normally
Monitor Azure Databricks in real-time and get notified instantly when it goes down. Track outages in Microsoft 365, Google Workspace, OpenAI, and 4,522+ services.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe. Sign up for free to see more Azure Databricks status data.
IsDown has tracked 127 incidents since started monitoring Azure Databricks status in January 2023. We collect data from 4522+ services, and normalize the data to give you a clear picture of the impact of the outage.
Date | Status | Incident | Duration |
---|---|---|---|
Oct 07, 2025
12:12 PM PDT
|
Minor | ES-1606227 | about 4 hours |
Sep 30, 2025
05:36 AM PDT
|
Minor | ES- | 8 minutes |
Sep 26, 2025
05:24 PM PDT
|
Major | ES-1597169 | about 6 hours |
Sep 20, 2025
06:56 PM PDT
|
Major | es-1591946 | 40 minutes |
Sep 15, 2025
11:16 PM PDT
|
Minor | ES-1586882 | about 3 hours |
Sep 15, 2025
08:14 AM PDT
|
Minor | ES-1586221 | about 3 hours |
Sep 12, 2025
08:06 PM PDT
|
Minor | ES-1584906 | about 1 hour |
Sep 10, 2025
04:30 AM PDT
|
Minor | ES-1581311 | about 7 hours |
Sep 05, 2025
12:08 AM PDT
|
Minor | ES-1570676 | about 1 hour |
Sep 04, 2025
08:01 AM PDT
|
Minor | ES-1569929 | about 1 hour |
One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.
Azure databricks on cus not responding
TypeError: super(type, obj): obj must be an instance or subtype of type
Can't view any for each loops in jobs.
Compute on databricks taking longer than expected. bombs out
Azure Databricks West Europe workspaces cannot be reached, jobs and cluster fail.
Databricks has experienced an error when loading. Catalogs disappeared
ODBC connectivity is impacted
Databricks API calls failing with either 503 or 504 issue.
Time 2025-07-03 11:56:17 CEST Message Failed to add 3 workers to the compute. Will attempt retry: false. Reason:Storage Download Failure Slow Help The VM setup took too long because the artifact downloading was slow. Please check your network configuration and try again or contact Databricks...
Clusters are failing to launch. Cluster launch will be retried.
Sql warehouses are down. All of them
Unable to load databricks Workspace getting error that Temporary un available
We are currently unable to access any of our Azure Databricks workspaces. All of them are failing to load and showing a “connection timed out” error at the login endpoint.
we have multiple instances of Azure Databricks, none of their Portal is opening.
Login fails, service down
Not able to connect to Databricks
Unable to load the web page
having randomly resolver errors
Unable to view compute. Sometimes visible, sometimes not with "Resolver Error". Degraded performance
Clusters not connecting - Resolver Error
Getting a Resolver Error while trying All-purpose compute and Job computes
Shared Compute cluster cannot be found (Resolver Error is thrown)
Not able to access any workflows or compute , "resolver issue"
cluster are not starting or visible
'Resolver error' in Compute
Databricks compute is not accessible. Getting Resolver error
Databricks compute is not accessible. Getting Resolver error
Clusters do not show up in the Compute tab
Jobs/Worflows will not list.
Nothing loading, folders empty, dashboard subscriptions not fulfilled. Unable to query/diagnose anything.
Data bricks is currently not working
Databricks portal is not working..... Spinning wheel.....
Databricks is down. UI and workspace can't be loaded
Issues with loading Databricks
Cannot login to azure databricks
Cannot log in - spinning wheel of death.
Barry can't load any page on databricks
Authentication issues to private workspace deployed in centralus
When attaching the cluster to a notebook and trying to run a cell, i get the message 'Waiting for compute to be ready'. This is happening on cluster that have been active for 30+ mins, so its not the usual delay when creating clusters.
Compute is extremely slow...
Entire platform in brazilsouth is down
Compute is extremely slow
"Resolver error" on Cluster list page
Resolver error and all compute clusters are not visible
Compute in-general seems to be down.
All clusters are missing from compute
Resolver error showing in compute
Resolver error and all of our clusters are gone.
Resolver error, no compute is visible on the workspace :(
Compute resources have been loading for hours, nothing happens.
Not able to access login page
Failed to set internal Spark configuration on all clusters in all environments, on both Classic and on Serverless All jobs started failing at 7:25 Jobs still work
Serverless is reporting "Failed to set internal Spark configuration" in West US 2 region.
Not able to access login page
Service is "TEMPORARILY_UNAVAILABLE"
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}
Server error 500 when deploying on databricks and accessing to notebooks
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}
Error Databricks has experienced an error when loading. Please wait a few minutes and refresh your browser.
Component | Status |
---|---|
API Service | OK |
Authentication Service | OK |
Compute Service | OK |
Jobs Service | OK |
Delta Live Tables | OK |
ODBC/JDBC Service | OK |
User Interface | OK |
Databricks SQL | OK |
Databricks SQL Serverless | OK |
Account Console | OK |
MLFlow | OK |
Services commonly monitored together with Azure Databricks and alternatives
Azure
Microsoft 365
AWS
Microsoft Office 365
Jira Software
Google Cloud
Salesforce
Zoom
Okta
Adobe
Akamai
GitHub
Slack
Confluence
Jira Service Management
Quickly access the status of Azure Databricks and 4,522+ services
Azure Databricks is a cloud-based analytics platform optimized for Microsoft Azure, integrating big data and machine learning with services for data processing and collaboration.
Monitoring Azure Databricks since January 2023
Tracking 11 Azure Databricks services and regions
49 incidents in 2025
Number of Incidents
8 issues
Last incident
0 days ago
Be the first to know when Azure Databricks goes down
Monitor All your Vendors in One Place
4522+ third-party services available to monitor
Know Before They Know
Alerts 30+ minutes before official updates
Stop the Ticket Flood
Cut "is it down?" tickets by 80%
IsDown aggregates various status pages from services into a very clear dashboard. Worth every penny.
Azure Databricks isn't down. You can check Azure Databricks status and incident details on the top of the page. IsDown continuously monitors Azure Databricks official status page every few minutes. In the last 24 hours, there were 1 outages reported.
Azure Databricks is currently operational. You can check Azure Databricks status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.
No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.
Currently there's no report of Azure Databricks being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the Azure Databricks official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
Azure Databricks last outage was on October 07, 2025 with the title "ES-1606227"
Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor Azure Databricks and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.
IsDown and DownDetector help users determine if Azure Databricks is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information instead of just relying on reports from users. The integration allows us to provide more details about Azure Databricks's Outages, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor Azure Databricks with maximum flexibility
IsDown monitors Azure Databricks for major outages. A major outage is when Azure Databricks experiences a critical issue that severely affects one or more services/regions. When Azure Databricks marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors Azure Databricks status page for minor outages. A minor outage is when Azure Databricks experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in Azure Databricks status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
IsDown monitors Azure Databricks and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
Azure Databricks and other vendors don't always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
The data and notifications you need, in the tools you already use.
14-day free trial · No credit card required · No code required