Databricks status: is it down right now?
Our own check of databricks.com from Europe and the US, every 3 minutes, with recent history.
databricks.com responded. The page answered normally in 135 ms.
databricks.com responded.
The page answered normally in 135 ms.
Checked (just now) from Europe and the US, automatic every 3 minutes.
Follow Databricks's public website. Free 10-minute checks, no card. This does not check every feature.
Run a website? Check my website
This checks the response from databricks.com. It does not test playback, login or every Databricks feature.
Databricks status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 5. A problem has to fail two checks in a row before we record it.
Watch your site free
This page is for their outage. Your own site can fail the same way. Free plan: 3 monitors, SSL alerts, no card.
Watch your site freeabout this service
About Databricks
Databricks is a lakehouse platform for data engineering, analytics, and AI/ML. Workspaces, clusters (Spark-based compute), Delta Lake, Unity Catalog (governance), Mosaic AI, and Databricks SQL are the main subsystems. It runs on AWS, Azure and GCP, and incidents are usually scoped to one cloud region. A workspace incident blocks notebook access; a cluster-provisioning incident blocks new compute but leaves running jobs alone; a Unity Catalog incident blocks new queries but cached permissions may keep existing sessions alive. Scheduled jobs (DLT pipelines, model training runs) hit failures first when a region is unhealthy.
The official Databricks status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster.
outage patterns
What outages typically look like on Databricks
Cloud platforms like Databricks rarely fail in obvious, all-or-nothing ways. The more common pattern is regional degradation: one availability zone or geographic region runs at half capacity while the rest of the platform serves traffic normally. Status pages often show green because the aggregate health check is still passing, even when a customer's specific workload is degraded.
The live tool above checks the public databricks.com endpoint from EU and US and compares status and response time. That can reveal a regional reachability problem, but it cannot prove that every Databricks product, API, or customer workload is healthy. Use the provider status reference and test the specific workflow you depend on before drawing a broader conclusion.
Common signs Databricks is having issues
- Temporarily unavailable pages or requests timing out during normal browsing
- Sustained response-time drift above the Databricks baseline (usually a precursor to hard failures)
- TLS handshake delays during peak hours that resolve at quieter times
- Regional disparity: one geography returns errors while another stays healthy
What to do when Databricks is degraded
If Databricks appears degraded, compare the EU and US endpoint results, open the provider status reference, and test the exact region and workflow your system uses. Preserve failed request IDs and timestamps for support. If only one region fails, use an alternate region only when your own failover policy permits it.
monitor 24/7
Monitor Databricks automatically.
Get independent alerts when the public Databricks endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Databricks on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Databricks uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Databricks down right now?
See the latest check of databricks.com and its timestamp at the top of this page. If Databricks is down, you can also check the official status page for extra context.
How do I check if Databricks is having issues?
This page checks the public Databricks endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Databricks goes down?
Set up a free monitor for databricks.com on Visual Sentinel for 10-minute checks with email and push alerts. Paid plans add checks as fast as 60 seconds and more notification channels.
Where can I find Databricks outage context?
The official Databricks status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster. Visual Sentinel checks the public Databricks endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why are new Databricks clusters failing to start during an outage?
Cluster provisioning depends on the underlying cloud (EC2 in AWS, VM Scale Sets in Azure). An incident in the Databricks control plane or the underlying cloud can block new clusters from launching, while existing clusters keep running until they auto-terminate.
Does a Databricks outage affect Delta Lake data stored in S3 or ADLS?
No. Delta Lake files live in your cloud storage and remain accessible via other tools. You temporarily lose Databricks-managed query features (Z-ordering, optimisation, compute) but the underlying data is not affected.