Azure Databricks status is operational
Updated
Tired of being the last to know about vendor outages? Get instant alerts when your cloud vendors experience downtime. Create a centralized status page to keep your team in the loop and minimize the impact of service disruptions.
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.
Donovan
11 days agoQuery is taking too long to run/not finishing.
Ibrahim
about 1 month agosite taking long to respond
Alex
about 2 months agoworkspace temporally unavailable
Gjimo
about 2 months agoDatabricks has experienced an error when loading. Please wait a few minutes and refresh your browser.
Ven
about 2 months ago"Databricks has experienced an error when loading. Please wait a few minutes and refresh your browser." sigh...
Shirisha
3 months agoDatabricks Sign-in page is on loop
Mario
3 months agoI'm stuck on "Screen is Loading" page while trying to login to Databricks Academy
Michael
3 months agoStuck on "Screen is Loading" page when attempting to login
Gra
3 months agoI can´t change my workspace
Bo
3 months agocan't sign into workspaces at all
Ven
3 months agoApi calls timeout or return error 500
Sri
3 months agoResponse not successful: Received status code 503
Ajit
3 months agoAzure Databricks is down...not able to login and run on job cluster
Piotr
3 months agoI'm getting an error Error Reload the page and try again. If the error persists, contact support.
Lukas
3 months agowest europe, all api calls failing
Ven
3 months agodatabricks returns webui errors and forces to reload page
Shaul
3 months agoUnable to upload files in dbfs
Ven
4 months agoAzure databricks status page shows it's operational, while workspace loads ages!
Jonas
4 months agosame as all others: temporarily uavailable
Robert
4 months agoError when logging in to workspace .TEMPORARILY_UNAVAILABLE
helena
4 months agodoesen't run. there's a problem. no further information.
J
4 months agoEverything temp unavailable
Gyuri
4 months agoThe service at https://adb-8502211284160771.11.azuredatabricks.net/?o=8502211284160771 is temporarily unavailable.
Stefan
4 months agoRuntime errors when submitting queries, allover
Mcnamara
4 months agoI am failing to access my workspace. Got error message Temporaril;y unavailable. Everything seems to be working fine now
Weronika
4 months agothe service is temporarily unavailable
Pedro
4 months ago"error_code": "TEMPORARILY_UNAVAILABLE" Server is unavailable
Ris
4 months agoError_code Temporarily unavailable
Ashwit
4 months agoThe page is assking for reload multiple times and error shows "Error fetching files. The service at /ajax-api/2.0/folders/list?order_by=node_name%20asc&page_size=100&parent=folders%2F3124641507204713&skip_owner_info=true is temporarily unavailable. Please try again later. [TraceId: -]"
Derk
4 months agoCan not access workspaces in west europe
Jay
4 months agoTemporarily unavailable errors, keep having to re-login (and failing as result)
Sebastian
4 months agoTemporarily unavailable error
Dinesh
4 months agoGetting error while trying to access azure databricks: {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /aad/auth?has=&l=en is temporarily unavailable. Please try again later. [TraceId: -]"}
Eliska
4 months agounable to connect to files, cluster
Ricardo
4 months agoNot loading anything, can't work with databrikcs
JC
4 months agoAzure west europe UI return error_code "TEMPORARILY_UNAVAILABLE" message "The service at /aad/redirect is temporarily unavailable. Please try again later. [TraceId: -]" Jobs started by API are OK.
Samuel
4 months agoDatabricks API returns 503 errors when trying to work in notebooks
Frank
4 months agoDatabricks API returns 503 errors
Christian
4 months agoCannot login into databricks {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /login.html is temporarily unavailable. Please try again later. [TraceId: -]"}
Atma
4 months agoCluster is terminating automatically
juan
4 months agoUser Interface interface is very very slow
Tony
4 months agoCompute isn't starting in Australia East
Vik
4 months agoCompure isnt starting on Azure Databricks
Andrew
4 months agosimple operation takes ages
sanket
4 months agoSlowness in the West Europe region
Christian
4 months agoGetting temporarily unavailable error
Job
4 months agoNotebooks are not starting, connection timeouts
R
4 months agoCompute clusters not loading packages
User
4 months agoLatency issue, taking 10mins to start a compute and another 10 to run imported packages (usually takes 2 mins)
Manu
4 months agoMLFlow Loading a simple PySpark ML linear regression doesn't work
Andrés
4 months agoClusters not properly importing libraries
Rick
4 months agoCannot access repository in workspace
Frank
4 months agoAuthentication is temporarily unavailable.
Arnab
4 months agoClusters are not starting up
Eric
4 months agoDatabricks Notebooks are not running.
joseph
4 months agocommands wont run or take ages to run
Silmaril
4 months agoClusters are running very slow
Nevena
4 months agoCLusters very slow or stop working
Mikael
4 months agoNotebooks don't run imports in Python
Tom
4 months agoAccess to storage (i.e. Workspace) from code seems not to be working
IsDown pulls data from Azure Databricks's status page every few minutes. Refresh the page every few minutes to see if there are any updates.
IsDown has tracked 75 incidents since started monitoring Azure Databricks status in January 2023.
12 days ago · lasted about 2 hours
Starting at approximately 18:44 UTC on October 23, 2024, customers may experience - Workspace authentication requests may fail or timeout. - Cluster start/resize/termination requests may fail or time out. - Jobs relying on cluster start/resiz... More details
13 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
about 1 month ago · lasted about 4 hours
We are actively investigating an intermittent issue affecting Databricks Serverless compute. Further updates will be provided within the next hour, or as events warrant. More details
We've tracked and collected 75 incidents since started monitoring Azure Databricks status
Number of Incidents
2 issues
Last incident
12 days ago
Tired of being the last to know about vendor outages? Get instant alerts when your cloud vendors experience downtime. Create a centralized status page to keep your team in the loop and minimize the impact of service disruptions.
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.
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.
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 23, 2024 with the title "ES-1289358"
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. Check more details in here.
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.
The data and notifications you need, in the tools you already use.
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime