Is Azure Databricks Down? Check the current Azure Databricks status

Azure Databricks is operational

Updated

Azure Databricks not working for you?

Monitoring Azure Databricks since January 2023. Learn more

Monitoring 11 Azure Databricks services and regions

8 incidents in 2025

Current Azure Databricks official ongoing incidents

No incidents reported in Azure Databricks's status page

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.

Azure Databricks issues reported by users in the last 24 hours

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.

Latest user comments about Azure Databricks problems

  • P

    Pete

    3 days ago

    Compute resources have been loading for hours, nothing happens.

  • M

    Mary

    9 days ago

    Not able to access login page

  • T

    Tristan

    29 days ago

    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

  • K

    Keno

    29 days ago

    Databricks SQL Serverless Serverless is reporting "Failed to set internal Spark configuration" in West US 2 region.

  • A

    Amit

    about 1 month ago

    Not able to access login page

  • I

    Iván

    about 1 month ago

    Service is "TEMPORARILY_UNAVAILABLE"

  • H

    Hmaidi

    about 1 month ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}

  • L

    Laia

    about 1 month ago

    Server error 500 when deploying on databricks and accessing to notebooks

  • Y

    Yue

    about 1 month ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}

  • G

    Gabi

    about 1 month ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}

  • N

    Nick

    about 1 month ago

    Error Databricks has experienced an error when loading. Please wait a few minutes and refresh your browser.

  • S

    Sreenivasan

    about 1 month ago

    Databricks workspace is temporarily unavailable. It is very slow and not responding.

  • S

    Stefan

    about 1 month ago

    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.

  • K

    Kjetil

    about 1 month ago

    Authentication is temproarily down

  • G

    Gavin

    about 1 month ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]"}

  • P

    Prateek

    about 1 month ago

    {"message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}

  • J

    Jan

    about 1 month ago

    Databricks workspace does not launch. Keeps returning "Databricks has experienced an error. Please wait a few minutes and refresh your browser"

  • M

    mukesh

    about 1 month ago

    got below error {"message":"Authentication is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}

  • A

    Amit

    2 months ago

    Azure data bricks is taking too much time to write a low volume data into ADLS

  • J

    John

    3 months ago

    Notebooks are not loading

  • A

    Abdul

    3 months ago

    Databricks is not loading

  • B

    Bram

    3 months ago

    I can't seem to reach the Azure Databricks Status page and DBFS is unreachable

  • K

    Kamil

    3 months ago

    Compute terminated. Reason: Cloud provider launch failure

  • D

    D.Smith

    3 months ago

    This site can’t be reached

  • S

    SurajB

    3 months ago

    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" }

  • O

    Otakar

    3 months ago

    Failed to execute query: The service at /ajax-api/2.0/lakeview-query/query/published is temporarily unavailable. Please try again later. [TraceId: -]

  • R

    Rumuz

    3 months ago

    "error_code": "TEMPORARILY_UNAVAILABLE"

  • A

    Anders

    3 months ago

    500 error, temporarily_unavailable

  • A

    Alexander

    3 months ago

    Cannot reach it and get a 500

  • T

    Tobias

    3 months ago

    "message": "The service at / is temporarily unavailable. Please try again later. "error_code": "TEMPORARILY_UNAVAILABLE"

  • L

    Luke

    3 months ago

    { "error_code": "500", "message": "INTERNAL_ERROR" }

  • C

    Chris

    3 months ago

    Reports "...temporarily unavailable. Please try again later." with the error code TEMPORARILY_UNAVAILABLE.

  • K

    KIko

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /?o=1804898655951190 is temporarily unavailable. Please try again later. [TraceId: -]"}

  • S

    Shiva

    3 months ago

    cannot launch the workspace

  • S

    Simon

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /editor/notebooks/1335651424310746?o=2406957283947115 is temporarily unavailable. Please try again later. [TraceId: -]"}

  • A

    Alexander

    3 months ago

    Error 500 for all workspaces in west europe

  • D

    David

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /?o=Xxxxxxxxxx is temporarily unavailable. Please try again later. [TraceId: -]"}

  • A

    amr

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}

  • M

    Marketa

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /editor/notebooks/1272199524678953?o=5769108933149883 is temporarily unavailable. Please try again later. [TraceId: -]"}

  • R

    Ric

    3 months ago

    unable to access the platform {"error_code":"500","message":"INTERNAL_ERROR"}

  • V

    Vincent

    3 months ago

    Service Temporarily unavailable

  • T

    Tim

    3 months ago

    {"message":"The service at /browse?o=3365325825638903 is temporarily unavailable. Please try again later. [TraceId: -]","error_code":"TEMPORARILY_UNAVAILABLE"}

  • G

    Geert

    3 months ago

    {"error_code":"500","message":"INTERNAL_ERROR"} West Europe

  • R

    Rudy

    3 months ago

    Can't access Databricks (West Europe)

  • A

    Andres

    3 months ago

    "error_code": "TEMPORARILY_UNAVAILABLE"

  • S

    Sebastian

    3 months ago

    { "error_code": "500", "message": "INTERNAL_ERROR" }

  • W

    Werner

    3 months ago

    Azure Databricks (region West Europe) is down for me. When trying to authenticate via Azure the response is: {"error_code":"500","message":"INTERNAL_ERROR"}

  • A

    Andrey

    3 months ago

    Can't access Azure Databricks workspace in west europe: {"error_code":"TEMPORARILY_UNAVAILABLE"}

  • M

    Marc

    3 months ago

    Can't connect to the workspace, West EU, error_code: 500

  • B

    Bryan

    3 months ago

    "error_code": "TEMPORARILY_UNAVAILABLE"

  • O

    Oliver

    3 months ago

    Majority of workspaces in west europe down

  • S

    Stijn

    3 months ago

    Can't access Azure Databricks workspace in west europe: {"error_code":"500","message":"INTERNAL_ERROR"}

  • C

    Connor

    3 months ago

    Unable to connect to workspace

  • A

    albert

    3 months ago

    "error_code": "TEMPORARILY_UNAVAILABLE",

  • A

    Andres

    3 months ago

    Azure DB is down, it's not working

  • V

    Viktor

    3 months ago

    Cannot access any Databricks workspace in the West Europe region

  • T

    Thomas

    3 months ago

    "error_code": "TEMPORARILY_UNAVAILABLE"

  • M

    mark

    3 months ago

    same here.... TEMPORARILY_UNAVAILABLE

  • E

    enri

    3 months ago

    {"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at / is temporarily unavailable. Please try again later. [TraceId: -]"}

  • R

    R

    3 months ago

    "TEMPORARILY_UNNAVAILABLE" message appears

Azure Databricks outage history

IsDown has tracked 88 incidents since started monitoring Azure Databricks status in January 2023.

  • Mar 03 2025
    ES-1373972

    9 days ago · lasted about 1 hour

    Between 14:16 UTC and 14:45 UTC March 03, 2025, customers may have experienced failures when interacting with unity catalog data objects. The issue has been mitigated. We will continue to monitor the platform and will provide a final update in ... More details

  • Feb 28 2025
    ES-1372187

    11 days ago · lasted about 1 hour

    We are actively investigating a cloud provider issue affecting Serverless compute. Further updates will be provided within the next hour, or as events warrant. More details

  • Feb 26 2025
    ES-1370605

    13 days ago · lasted about 2 hours

    Starting at approximately 18:45 UTC on February 26, 2025, customers may experience failures when attempting to launch clusters and serverless compute resources, DBSQL Warehouse launch failures and disruptions in workspace creation. Our cloud pr... More details

  • Jan 2023 ...
    IsDown started monitoring Azure Databricks status

    We've tracked and collected 88 incidents since started monitoring Azure Databricks status

Sign up and check all outage history

Azure Databricks outages in the last 30 days

Number of Incidents

5 issues

Last incident

9 days ago

Having problems with Azure Databricks? What can you do?

  1. First, stay calm.

    • We know it's stressful when Azure Databricks is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.

  2. Make a quick evaluation of the impact

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did Azure Databricks already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Azure Databricks status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.

  3. Communicate with your team and users quickly

    • If Azure Databricks is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.

  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.

  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.

  6. Service has recovered?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.

  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.

  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.
Official Status Pages + User Reports

The best way to monitor Azure Databricks and other dependencies

Get instant alerts when your critical services go down. One dashboard to monitor all your vendors' status pages.

Start Your Free Trial
14-day free trial No credit card required Cancel anytime
Be the first to know when Azure Databricks and other third-party services go down

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.

Start Free Trial 14-day free trial · No credit card required · 3200+ cloud vendors available

Companies that monitor Azure Databricks also follow the status of these services

Azure
OK
Microsoft 365
OK
Jira Software
OK
Google Cloud
OK
Zoom
OK
Okta
OK
Microsoft Office 365
MAJOR
AWS
OK
Salesforce
MINOR
GitHub
OK
Confluence
OK
Jira Service Management
OK
Snyk
OK
Google Workspace
OK
Adobe
MINOR

Stay informed about Azure Databricks status changes

IsDown offers an easy way to monitor Azure Databricks with maximum flexibility

Major Outages Notifications

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.

Minor Outages 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.

Outage Details

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.

Component Filtering

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.

Early Outage Indicators

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.

Frequently Asked Questions

Is Azure Databricks down today?

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.

What is the current Azure Databricks status?

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.

Is there a Azure Databricks outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is Azure Databricks slow today?

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.

How are Azure Databricks outages detected?

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.

When was the last Azure Databricks outage?

Azure Databricks last outage was on March 03, 2025 with the title "ES-1373972"

Azure Databricks not working for you? How do I know if Azure Databricks is down?
  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.
How can I check Azure Databricks status and outages?
Why use IsDown to monitor Azure Databricks instead of the official status page?

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.

How IsDown compares to DownDetector?

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.

“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.”

Laurent D., Lead SRE & Platform
We play well with others

Get Azure Databricks outage notifications where you need them the most

The data and notifications you need, in the tools you already use.

Slack logo
Slack Datadog logo
Datadog PagerDuty logo
PagerDuty Opsgenie logo
Opsgenie Zendesk logo
Zendesk Rootly logo
Rootly FireHydrant logo
FireHydrant StatusHub logo
StatusHub Google Chat logo
Google Chat Microsoft Teams logo
Microsoft Teams SquaredUp logo
SquaredUp Squadcast logo
Squadcast Crisp logo
Crisp
Zapier logo
Zapier
Discord logo
Discord

Email
Webhooks

Webhooks

Latest Articles from our Blog

What is a Status Page? All You Need to Know

What is a Status Page? All You Need to Know

What is a status page? See how, as an effective incident management tool offering streamlined incident communication, it enhances stakeholder satisfaction.
Top StatusTicker Alternatives for Outage Monitoring in 2025

Top StatusTicker Alternatives for Outage Monitoring in 2025

Get to know the top 2025 alternatives to StatusTicker for monitoring outages. Explore tools that help you maximize status updates of third party performance.
Stop using Status Pages RSS Feeds in Slack

Stop using Status Pages RSS Feeds in Slack

Managing RSS feeds in Slack for outage updates is getting harder. It can cause confusion and inefficiency. We have a better way.
See all the blog articles

Never again lose time looking in the wrong place

Start Monitoring in 5 minutes

14-day free trial · No credit card required · No code required