Azure Databricks Status - Is Azure Databricks Down?
Azure Databricks is operational
Updated
Azure Databricks is operational
Updated
IsDown pulls data from Azure Databricks's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
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.
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
Arun
Compute is extremely slow...
Fabiano
Entire platform in brazilsouth is down
Pim
Compute is extremely slow
Aleksandr
"Resolver error" on Cluster list page
Philip
Resolver error and all compute clusters are not visible
Farooq
Compute in-general seems to be down.
Don
All clusters are missing from compute
Steve
Resolver error showing in compute
Grant
Resolver error and all of our clusters are gone.
Vincent
Resolver error, no compute is visible on the workspace :(
Pete
Compute resources have been loading for hours, nothing happens.
Mary
Not able to access login page
Tristan
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
Keno
Serverless is reporting "Failed to set internal Spark configuration" in West US 2 region.
Amit
Not able to access login page
Iván
Service is "TEMPORARILY_UNAVAILABLE"
Hmaidi
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}
Laia
Server error 500 when deploying on databricks and accessing to notebooks
Yue
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}
Gabi
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}
Nick
Error Databricks has experienced an error when loading. Please wait a few minutes and refresh your browser.
Sreenivasan
Databricks workspace is temporarily unavailable. It is very slow and not responding.
Stefan
I have this error while loading my workspace: Error Databricks has experienced an error when loading. Please wait a few minutes and refresh your browser.
Kjetil
Authentication is temproarily down
Gavin
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}
Prateek
{"message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}
Jan
Databricks workspace does not launch. Keeps returning "Databricks has experienced an error. Please wait a few minutes and refresh your browser"
mukesh
got below error {"message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}
Amit
Azure data bricks is taking too much time to write a low volume data into ADLS
John
Notebooks are not loading
Abdul
Databricks is not loading
Bram
I can't seem to reach the Azure Databricks Status page and DBFS is unreachable
Kamil
Compute terminated. Reason: Cloud provider launch failure
D.Smith
This site can’t be reached
SurajB
Launching the workspace returns a 500 internal error. Retrying through an incognito browser returns a different error: { "message": "The service at / is temporarily unavailable. Please try again later. [TraceId: -]", "error_code": "TEMPORARILY_UNAVAILABLE" }
Otakar
Failed to execute query: The service at /ajax-api/2.0/lakeview-query/query/published is temporarily unavailable. Please try again later. [TraceId: -]
Rumuz
"error_code": "TEMPORARILY_UNAVAILABLE"
Anders
500 error, temporarily_unavailable
Alexander
Cannot reach it and get a 500
Tobias
"message": "The service at / is temporarily unavailable. Please try again later. "error_code": "TEMPORARILY_UNAVAILABLE"
Luke
{ "error_code": "500", "message": "INTERNAL_ERROR" }
Chris
Reports "...temporarily unavailable. Please try again later." with the error code TEMPORARILY_UNAVAILABLE.
KIko
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /?o=1804898655951190 is temporarily unavailable. Please try again later. [TraceId: -]"}
Shiva
cannot launch the workspace
Simon
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /editor/notebooks/1335651424310746?o=2406957283947115 is temporarily unavailable. Please try again later. [TraceId: -]"}
Alexander
Error 500 for all workspaces in west europe
David
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /?o=Xxxxxxxxxx is temporarily unavailable. Please try again later. [TraceId: -]"}
amr
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}
Marketa
{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /editor/notebooks/1272199524678953?o=5769108933149883 is temporarily unavailable. Please try again later. [TraceId: -]"}
Ric
unable to access the platform {"error_code":"500","message":"INTERNAL_ERROR"}
Vincent
Service Temporarily unavailable
Tim
{"message":"The service at /browse?o=3365325825638903 is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}
Geert
{"error_code":"500","message":"INTERNAL_ERROR"} West Europe
Rudy
Can't access Databricks (West Europe)
Andres
"error_code": "TEMPORARILY_UNAVAILABLE"
Sebastian
{ "error_code": "500", "message": "INTERNAL_ERROR" }
Werner
Azure Databricks (region West Europe) is down for me. When trying to authenticate via Azure the response is: {"error_code":"500","message":"INTERNAL_ERROR"}
Andrey
Can't access Azure Databricks workspace in west europe: {"error_code":"TEMPORARILY_UNAVAILABLE"}
Marc
Can't connect to the workspace, West EU, error_code: 500
Bryan
"error_code": "TEMPORARILY_UNAVAILABLE"
IsDown has tracked 94 incidents since started monitoring Azure Databricks status in January 2023.
6 days ago · lasted about 1 hour
We are actively investigating an issue with the Databricks service. Further updates will be provided within the next hour, or as events warrant. More details
9 days ago · lasted 24 minutes
Starting at approximately 00:00 UTC April 15, 2025, customers may experience failures when attempting to launch all-purpose and jobs compute resources. We are currently investigating. Further updates will be provided in 1 hour, or as events war... More details
17 days ago · lasted about 1 hour
All Azure Databricks Services are unavailable in Brazil South. This is being actively investigated. Status Updates will be provided in 1 hour, or as things progress. More details
We've tracked and collected 94 incidents since started monitoring Azure Databricks status
Monitoring 11 Azure Databricks services and regions
15 incidents in 2025
Number of Incidents
3 issues
Last incident
6 days ago
Azure
Microsoft 365
Jira Software
Google Cloud
Zoom
Okta
Microsoft Office 365
AWS
Salesforce
GitHub
Confluence
Jira Service Management
Snyk
Google Workspace
Adobe
Why teams choose IsDown:
14-day free trial • No credit card required
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
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 0 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 April 18, 2025 with the title "ES-1430020"
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 a service 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. The integration allows us to provide more details about the outage, 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.
“Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.”
The data and notifications you need, in the tools you already use.
14-day free trial · No credit card required · No code required
