AWS Databricks Status - Is AWS Databricks Down?

AWS Databricks is operational

Updated

AWS Databricks not working for you?

Current AWS Databricks official ongoing incidents

No incidents reported in AWS Databricks's status page

IsDown pulls data from AWS Databricks's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.

AWS 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 AWS Databricks problems

  • C

    Cynthia

    AWS VA-East Databricks pages are slow to load and some aren't loading at all. The Catalog is popping up with an interface I've never seen before, which prompts to me add live compute before I can access the Catalog.

  • S

    samiksha

    Community Edition

    This site can’t be reached Check if there is a typo in community.databricks.com. If spelling is correct, try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN

  • Á

    Álvaro

    Can't access Databricks workspace hosted on AWS eu-central-1.

  • J

    Jacob

    Databricks Catalog has an issue: Error getting schemas Unsupported response format: STREAM The data is still available via querying but nothing can be seen in the catalog

  • A

    Ari

    Unsupported response format: STREAM in Unity Catalog access

  • R

    Ritik

    Community Edition

    DBFS storage is no more accessible. I get this error whenever I try to open it from the URL or try to access it from code. "Failed to upload command result to DBFS. Error message: Status code: 301 Moved Permanently, Error message: PermanentRedirectThe bucket you are attempting to access must b...

  • V

    Vikas

    Community edition login is not working

  • C

    Chris

    Community Edition

    Log in does nothing. No error and no sign-in for valid username and password.

  • F

    Felipe

    Cannot login to my workspaces, but can login to my dashboard.

  • B

    Ben

    Unable to login

  • M

    Milton

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

Real-time vendor status monitoring for IT and Ops teams

Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.

Start Monitoring Your Vendors 14-day free trial · No credit card required · No setup required - just add your vendors

AWS Databricks outage history

IsDown has tracked 57 incidents since started monitoring AWS Databricks status in January 2023.

  • Apr 04 2025

    26 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

  • Apr 02 2025

    28 days ago · lasted about 1 hour

    Starting at approximately 11:06 UTC April 02, 2025, customers may experience failures when attempting to launch job and all-purpose compute resources. We are currently investigating. Further updates will be provided in 1 hour, or as events warr... More details

  • Mar 14 2025

    about 2 months ago · lasted 44 minutes

    Starting at approximately 21:00 UTC March 14, 2025 customers may experience an interruption to their Compute Services. Please refer to https://health.aws.amazon.com/health/status for more information We are currently investigating. Further... More details

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

    We've tracked and collected 57 incidents since started monitoring AWS Databricks status

Sign up and check all outage history

Having problems with AWS Databricks? What can you do?

  1. First, stay calm.

    • We know it's stressful when AWS 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 AWS Databricks already acknowledge the issue? And published a status update? (You can find it in the top of the page or in AWS 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 AWS 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 aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.

Be the first to know when AWS Databricks is down (and all your dependencies)

Instant Outage Alerts

Get notified on Slack, Datadog, Incident.io and more

Unified Dashboard

Monitor all vendors status in one place

Status Pages

Create private or public status pages

Historical Data

Track uptime over time in all your vendors

Start Monitoring your Vendors
14-day free trial No credit card required
Learn more about IsDown

Monitoring 12 AWS Databricks services and regions

10 incidents in 2025

AWS Databricks outages in the last 30 days

Number of Incidents

2 issues

Last incident

26 days ago

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

Monitor All Your Services

Why teams choose IsDown:

  • ✓ Real-time alerts for AWS Databricks and 3850+ cloud services
  • ✓ Unified dashboard for all your vendors
  • ✓ Custom status pages for your team

14-day free trial • No credit card required

Real-time vendor status monitoring for IT and Ops teams

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 Monitoring Your Vendors 14-day free trial · No credit card required · No setup required - just add your vendors

Frequently Asked Questions

Is AWS Databricks down today?

AWS Databricks isn't down. You can check AWS Databricks status and incident details on the top of the page. IsDown continuously monitors AWS Databricks official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current AWS Databricks status?

AWS Databricks is currently operational. You can check AWS 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 AWS 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 AWS Databricks slow today?

Currently there's no report of AWS Databricks being slow. Check on the top of the page if there are any reported problems by other users.

How are AWS Databricks outages detected?

IsDown monitors the AWS 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 AWS Databricks outage?

AWS Databricks last outage was on April 04, 2025 with the title "ES-1412507"

AWS Databricks not working for you? How do I know if AWS 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 AWS Databricks status and outages?

Why use IsDown to monitor AWS 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 AWS 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.

Want to be informed about AWS Databricks status changes?

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

Major Outages Notifications

IsDown monitors AWS Databricks for major outages. A major outage is when AWS Databricks experiences a critical issue that severely affects one or more services/regions. When AWS 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 AWS Databricks status page for minor outages. A minor outage is when AWS 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 AWS 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 AWS Databricks and all their 12 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

AWS 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.

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

We play well with others

Get AWS Databricks outage notifications where you need them the most

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

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

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