Skip to main content
Databricks logo

Is Databricks Down?

No — Databricks is up
Databricks's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 226 ms

Right now

The verdict is the worse of these two. How we decide

Databricks's status page

status.databricks.com · read · checked every 3 minutes

Operational
Databricks's components, as its status page reports them
ComponentStatus
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Northeast 1Operational
149 more, all operational · show all 161
All of Databricks's components
ComponentStatus
Agent Bricks
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Northeast 1Operational
AP Northeast 2Operational
AI/BI
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Compute
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Databricks Apps
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Northeast 1Operational
AP Northeast 2Operational
Databricks SQL
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Genie
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Lakebase
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Northeast 1Operational
Lakeflow
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Notebooks
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational
US Gov West 1Operational
US West 2Operational
SA East 1Operational
AP South 1Operational
AP Southeast 1Operational
AP Southeast 2Operational
AP Southeast 3Operational
AP Northeast 1Operational
AP Northeast 2Operational
Unity Catalog
CA Central 1Operational
EU West 1Operational
EU West 2Operational
EU West 3Operational
EU Central 1Operational
US East 1Operational
US East 2Operational
US West 1Operational

And 11 more that Databricks lists, not shown here.

Open their status page

FlareWarden checks

databricks.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
226 ms
Checked

By region

  • Ashburn reachable, 251 ms
  • Dallas reachable, 300 ms
  • Frankfurt reachable, 107 ms
  • Johannesburg reachable, 434 ms
  • Los Angeles reachable, 208 ms
  • Newark reachable, 224 ms
  • Paris reachable, 145 ms
  • São Paulo reachable, 146 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn135 ms1 ms21 ms239 ms
Dallas147 ms1 ms12 ms291 ms
Frankfurt19 ms2 ms10 ms87 ms
Johannesburg208 ms1 ms10 ms419 ms
Los Angeles77 ms3 ms19 ms191 ms
Newark130 ms2 ms12 ms210 ms
Paris38 ms2 ms15 ms134 ms
São Paulo53 ms2 ms15 ms132 ms
We check that databricks.com loads, not every feature behind it. Test it yourself

History

Incidents Databricks reported

Since Oct 27, 10 days · from status.databricks.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Databricks website availability

Measured by FlareWarden · databricks.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
246ms

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 31 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 31 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of databricks.com from multiple regions every 6 hours. Databricks's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Databricks does

Databricks is a data and AI platform built around the lakehouse model, combining notebooks, SQL warehouses, pipelines and machine learning on top of cloud storage. Data teams schedule production jobs on it, so an incident usually shows up first as overnight pipelines that failed rather than as people unable to log in.

What an outage looks like

Clusters fail to start or hang in a pending state, so notebooks attach to nothing. Scheduled jobs fail at launch and the failure is only noticed the next morning. SQL warehouses will not resume, leaving dashboards timing out. Unity Catalog problems block table access while compute is healthy, and notebooks may open while every command queues.

What to do about it

Check status.databricks.com, which reports Compute, Databricks SQL, Notebooks, Unity Catalog and Lakeflow separately across many cloud regions, and also tracks dependencies including AWS EC2, S3 and Route 53. Confirm your workspace region first. Let failed jobs be rerun deliberately rather than by an automatic retry storm against a platform that is still recovering.

Is it down for everyone, or just you?

If this page says Databricks is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Snowflake
Snowflake
AWS
AWS
MongoDB Atlas
MongoDB Atlas
Datadog
Datadog

Databricks outage FAQ

Is Databricks down or is my cluster just slow to start?
Cluster startup normally takes several minutes while cloud instances are provisioned, which is easy to mistake for a hang. Check status.databricks.com for your region and the Compute component. If the region is healthy, look at instance availability and quota in your cloud account, which cause more startup failures than Databricks incidents do.
Which region should I check on the Databricks status page?
The one your workspace runs in, visible in the workspace URL. Databricks lists many regions across cloud providers and incidents are usually confined to one. The status page also tracks upstream dependencies such as AWS EC2 and S3, which is useful when the underlying cause is the cloud provider rather than Databricks itself.
Will failed jobs rerun automatically after an outage?
Only if you configured retries, and aggressive retries against a recovering platform can make things worse. Jobs that failed at launch usually need a deliberate rerun once the status page is clear. Check for partial writes first: a job that failed midway may have committed some output, and rerunning it blindly can duplicate data.
Why can I open a notebook but not run anything?
The workspace interface and the compute layer are separate. Serving a notebook is lightweight, while running a command needs a cluster, so the editor loads during incidents that stop execution entirely. Check the Compute component rather than concluding from a working notebook that the platform is healthy and the problem is your code.
Does a Databricks outage put my data at risk?
Data sits in your own cloud storage rather than inside Databricks, so an incident affects the ability to process it, not its durability. The exposure is to jobs interrupted mid-write, which can leave partial output. Checking the state of tables written by any job that failed is worth doing before rerunning anything.

How we measure this

  • We request Databricks's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Databricks publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Databricks itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Databricks goes down

We check Databricks every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required