Last updated: November 11, 2026
Is Databricks down? User reports show no current problems with Databricks
Databricks is a data and AI platform built on Apache Spark for data engineering, SQL analytics and machine learning. Teams work in cloud workspaces with clusters, notebooks, jobs and SQL warehouses.
Report a problem !
Select which issue applies
Databricks problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate Databricks over the past 3 months?
Most reported locations
Where Databricks reports are coming from in the last 24 hours.
No problem locations to show yet. Databricks looks fine right now. Locations appear here as soon as users submit reports.
Latest Databricks user reports
No reports yet — be the first to report a problem above.
Databricks outage history
The live report status for Databricks, updated as reports come in.
Good news. Databricks has no reported problems right now. If it is not working for you, report it above and your report will appear here.
Databricks uptime and reports
Live report counts and the day by day record for the last 30 days.
User reports received in each period.
Last 30 days, day by day: 12 October 2026 to 10 November 2026
Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.
The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.
Get Databricks down alerts
Leave your email and we will tell you when Databricks is having problems, and when it is back up. No spam.
Databricks on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying Databricks is down. Checked 11 November 2026, 3:50 AM PKT.
Quiet right now. Nobody on Bluesky is saying Databricks is down.
Guides that can fix it
Step by step fixes for the problems people report most.
→ An App Is Not Working? Fixes for Android and iPhone
→ Login Problems That Are Not an Outage
→ How to Clear the Cache in Firefox, Safari and Edge
Is Databricks Down Right Now?
Databricks is not down for most users right now. Reports here come from engineers who run workspaces, clusters and SQL warehouses every day. A fast spike in reports often matches a cloud region problem.
Many Databricks errors look scary but start small. A stuck cluster or an expired token can block one person while the platform stays up. Use the checks below before you call it a full Databricks outage.
Is Databricks Down for Me or Everyone?
Open a second workspace or the Databricks status view for your cloud. If other workspaces load, the platform is fine and your workspace or network is the problem. Try the workspace from a phone hotspot to test your office network. If it loads there, your firewall or DNS is blocking the real address.
Clusters Stuck on Starting
The classic Databricks headache is a cluster that sits in starting forever. The control plane is fine, but the cloud cannot give it machines. Spot capacity, a busy region, or a wrong VM size can all block the start. Video engineers on the same floor render in DaVinci Resolve while a cluster boots, so a slow start reshuffles two jobs at once.
Open the cluster event log to see the real reason. Try a smaller or different VM type, or switch spot off for a test.
Workspace Page Will Not Load
Sometimes the workspace login page spins and never finishes. Rate limits can block your IP after heavy API use, which returns 429 errors. Firewalls and security groups can also cut the path to the workspace.
Test from another network, like a phone hotspot, to confirm. If it loads there, your office network rules need a fix. Wait out a 429 block instead of retrying in a loop, since retries extend it.
Tokens and 403 Errors
Scripts and tools break when a personal access token expires. The job then fails with a 403 or a plain connection error. The real cause hides in the job log, not in the code.
Create a fresh token and store it in your secret scope. Update the tool or notebook that used the old one.
Notebooks Detached and Jobs Failing
A notebook can detach when its cluster restarts or terminates. Your code stays, but the session and variables are gone. Auto termination is the usual silent cause during long breaks.
Reattach the notebook to a running cluster and rerun the setup cells. Raise the auto termination time for long work. For failed jobs, read the driver log first, since the top error names the failed step.
Common Databricks Problems and Fixes
Read the Cluster Event Log
Open the cluster page and read the event log before you change anything. It names capacity, network and setup errors in plain words. Fix the cause it shows, then start the cluster again.
Change the VM Type
Edit the cluster and pick a different VM family or a smaller size. Turn off spot instances for the test run. If the new shape starts fast, capacity was your whole problem.
Replace an Expired Token
Go to user settings and create a new personal access token. Update every script and tool that used the old token. Delete the old token so nobody picks it by mistake.
Check Your Network Path
Load the workspace from a phone hotspot or home network. If it works there, your office firewall or DNS is at fault. Share the workspace address with your network team so they can allow it.
Restart a Stuck SQL Warehouse
Stop the SQL warehouse fully, wait a minute, then start it again. A warehouse stuck after a config change often clears this way. Check the event history if it fails a second time.
Having a problem with Databricks?
Comments are public and help others understand the issue.
Frequently Asked Questions
Why is my Databricks cluster stuck on starting?
The cloud cannot give the cluster its machines yet. Spot shortages and busy regions are common causes. Read the cluster event log for the exact reason. Trying a different VM type often starts at once.
What does RESOURCE_EXHAUSTED mean in Databricks?
It means the cloud region ran out of the capacity your cluster asked for. Databricks retries the launch on its own for a while. You can pick a smaller VM type or another region. Peak hours make this error more likely.
Why does my Databricks workspace never finish loading?
A rate limit or a network block is the usual cause. Heavy API use can earn your IP a 429 block. Test the workspace from a phone hotspot. If it loads there, your office network or the block is the problem.
Why do I get a 403 error from Databricks?
An expired or wrong personal access token causes most 403 errors. Create a fresh token in user settings. Update the script or tool that connects. Jobs fail at once when a token dies, even with no code change.
Why did my Databricks notebook detach?
The cluster under the notebook restarted or terminated. Auto termination after idle time is the top cause. Reattach the notebook to a running cluster. Then rerun your setup cells to rebuild variables.
Why won’t my Databricks SQL warehouse start?
Capacity limits and bad config changes block warehouse starts. Stop it fully and start it again first. Read the event history for quota or network errors. Your admin can raise quotas if the log points that way.