Is Docker Down? Check the current Docker status

Docker is operational

Updated

Docker not working for you?

Monitoring Docker since March 2022. Learn more

Monitoring

10 components

Total Incidents in 2025

10 incidents

Official Information + User Reports = #1 Status Aggregator

The best way to monitor Docker and other dependencies

IsDown aggregates the status pages of all your critical services. Receive alerts and create one dashboard with all your vendors.

Start monitoring Docker
14-day free trial · No credit card required · Cancel anytime

Current Docker official ongoing incidents

No incidents reported in Docker's status page

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

Docker 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 Docker problems

  • R

    Rick

    4 days ago

    Docker Hub Registry Can´t pull docker images from docker-hub - Step 1/27 : FROM hub.docker.highway.porsche.com/node:18.20.0-alpine as builder 18.20.0-alpine: Pulling from node 4abcf2066143: Pulling fs layer 2694e4502e24: Pulling fs layer f8ecf2fb4bd9: Pulling fs layer d3da4a73e4df: Pulling fs layer d3da4a73e4d...

  • L

    Leanne

    5 days ago

    Job for docker.service failed because the control process exited with error code. I tried to restart my machine and reinstall Docker, but that does not seem to help. Any docker commands do not work

  • F

    Francesco

    16 days ago

    Docker Hub Registry Failed to pull image "docker.io/istio/operator:1.22.8": failed to pull and unpack image "docker.io/istio/operator:1.22.8": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/istio/operator/blobs/sha256:c8091252263827107b8ba805e325a03c307b7c26bca119...

  • P

    Pratham

    16 days ago

    Docker Hub Registry python:3.11-slim-bullseye not able to pull

  • M

    magy

    16 days ago

    Docker Hub Registry cannot pull containers 500err

  • S

    Sam

    16 days ago

    Docker Hub Registry got 500 Internal Server Error

  • T

    Tom

    16 days ago

    Docker Hub Registry Docker Hub servers report http 500 errors when pulling images.

  • J

    Jawad

    16 days ago

    Docker Hub Registry Unable to pull and push images to docker.io recieving Internal server error 500

  • M

    Milan

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error (manager.go:254:7s)

  • C

    CHIHYU

    16 days ago

    Docker Hub Registry 500 error when pulling images

  • M

    Mengz

    16 days ago

    Docker Hub Registry Failed to pull public images. ``` $ docker image pull vikunja/vikunja:0.24.6 0.24.6: Pulling from vikunja/vikunja a968a69f52dd: Retrying in 1 second 5e115961be39: Retrying in 1 second 6285d5f3f8bb: Retrying in 1 second error pulling image configuration: download failed after attempts=6: re...

  • O

    Ozan

    16 days ago

    Docker Hub Registry Can't pull images, 500 error

  • S

    Sukh

    16 days ago

    Docker Hub Registry Meanwhile Docker Hub is down, use Google's mirror for now: "registry-mirrors": ["https://mirror.gcr.io"]

  • A

    Alix

    16 days ago

    Docker Hub Registry 500 internal error on pull

  • H

    hakima

    16 days ago

    Docker Hub Registry latest: Pulling from library/ubuntu : Retrying in 1 second error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error Got this error

  • P

    Phong

    16 days ago

    ERROR: Job failed: failed to pull image "docker:dind" with specified policies [always]: error pulling image configuration: download failed after attempts=6

  • H

    Han

    16 days ago

    Docker Hub Registry No able to pull from DockerHub

  • V

    Veaceslav

    16 days ago

    Docker Hub Registry docker pull docker:latest returning 500 status code

  • I

    Ivo

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • A

    Aladin

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • M

    martin

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • R

    Ramon

    16 days ago

    Docker hub registry returning 500 errors

  • P

    Patrick

    16 days ago

    Docker Hub Web Can't pull images: error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • A

    Adam

    16 days ago

    Docker Hub Registry 500 Internal Server Error

  • J

    Johannes

    16 days ago

    Docker Hub Registry error pulling image download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • S

    Shobhit

    16 days ago

    Docker Hub Registry Docker Hub is responding with ISE (500)

  • M

    Madhusudan

    16 days ago

    Docker Hub Registry giving 500 while pulling python image

  • B

    bharat

    16 days ago

    Docker Hub Registry docker is down error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • M

    Mykhailo

    16 days ago

    Docker Hub Registry unexpected status code 500 Internal Server Error

  • J

    JANOS

    16 days ago

    Docker Hub Registry Cannot pull image from hub

  • R

    Rio

    16 days ago

    Docker Hub Registry We cannot build docker image

  • A

    Andy

    16 days ago

    Docker Hub Registry Getting HTTP req error code 500

  • T

    Tobias

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • D

    dom

    16 days ago

    Docker Hub Registry 500 Internal Server Error when pulling image

  • E

    Eero

    16 days ago

    Docker Hub Registry 500 Internal Server Error

  • D

    Denys

    16 days ago

    Docker Hub Registry error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error

  • L

    Lajos

    16 days ago

    Docker Hub Registry failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/mariadb/blobs/sha256:d045ae11ce7ea8529ff420da5b7f4f19302c0824db2b81be3fed1a2ca8c4e639: 500 Internal Server Error

  • P

    Paul

    16 days ago

    Docker Hub Registry Getting 500 internal server error trying to pull otel/opentelemetry-collector-contrib:latest

  • F

    Farhan

    16 days ago

    Docker Hub Registry Dockerhub is down not able to pull images getting 500 error

  • K

    Kamil

    16 days ago

    Docker Hub Registry `500 Internal Server Error` on image download

  • T

    tomer

    16 days ago

    Docker Hub Registry get status 500 for pulling golang:1.21.3 image

  • R

    RK

    16 days ago

    Docker Hub Registry Not able to pull image, It is throwing 500

  • I

    Igor

    16 days ago

    Docker Hub Registry Failed to pull image "docker:20.10.6"

  • K

    Kerenke

    16 days ago

    Docker Hub Registry I can't pull images getting error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error`

  • A

    Adriaan

    16 days ago

    Can't pull images from the Docker registry.

  • A

    Artyom

    16 days ago

    ERROR: failed to solve: node:14-alpine: failed to resolve source metadata for docker.io/library/node:14-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/node/blobs/sha256:0dac3dc27b1ad570e6c3a7f7cd29e88e7130ff0cad31b2ec5a0f222fbe9...

  • H

    Het

    25 days ago

    I have installed docker, it says docker is in use but not responding. I can't open Docker. I have uninstalled it and install again, no change.

  • I

    isaac

    4 months ago

    Docker Hub Registry not accesible from where i am tested in my connection and outside

  • E

    Erik

    5 months ago

    Docker Hub Registry Error response from daemon: Get "https://registry-1.docker.io/v2/": unauthorized: incorrect username or password

  • D

    Doug

    5 months ago

    Docker Hub Registry Personal Access Token authentication is broken

  • S

    Sam

    5 months ago

    Docker Hub Registry Website content not loading. 408 error

  • T

    Terrence

    5 months ago

    Can't authenticate to use my PAID Docker account

  • M

    Marco

    5 months ago

    Docker Hub Registry I am pulling postgres:16 image and I am getting a 500 error

  • B

    Benjamin

    6 months ago

    Docker Hub Registry Cant pull images with TLS handshake timeout. Docker hub page also not loading

  • T

    Tim

    6 months ago

    TLS timeout on arbitrary image pull

  • D

    D

    6 months ago

    > Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout

  • A

    Aditya

    6 months ago

    Docker Hub Registry Not able to download any docker image

  • A

    Ari

    6 months ago

    Docker Desktop is stuck in starting mode

  • K

    Kaustubh

    6 months ago

    Docker Hub Registry I cannot sign in in docker hub registry

  • E

    Edwin

    7 months ago

    Docker Hub Registry Something went wrong! We've logged this error and will review it as soon as we can. If this keeps happening, please file a support ticket with the below ID.

Docker outage history

IsDown has tracked 65 incidents since started monitoring Docker status in March 2022.

Sign up and check all outage history

Docker outages in the last 30 days

Number of Incidents

6 issues

Last incident

2 days ago

Having problems with Docker? What can you do?

  1. First, stay calm.

    • We know it's stressful when Docker 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 Docker already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Docker 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 Docker 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.
Be the first to know when Docker 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 Docker also follow the status of these services

GitHub
OK
AWS
OK
Slack
OK
Google Workspace
OK
Jira Software
OK
Cloudflare
MINOR
Zoom
OK
Google Cloud
OK
Datadog US1
OK
Microsoft 365
OK
Confluence
OK
Azure
OK
Zendesk
OK
Okta
OK
Microsoft Office 365
OK

Stay informed about Docker status changes

IsDown offers an easy way to monitor Docker with maximum flexibility

Major Outages Notifications

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

Docker 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 Docker down today?

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

What is the current Docker status?

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

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

How are Docker outages detected?

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

Docker last outage was on February 20, 2025 with the title "Signup issue"

Docker not working for you? How do I know if Docker is down?
How can I check Docker status and outages?
Why use IsDown to monitor Docker 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 Docker 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 Docker 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

Best StatusSight Alternatives for Vendor Monitoring

Best StatusSight Alternatives for Vendor Monitoring

Discover the best alternatives to StatusSight for monitoring SaaS and cloud services in 2025. Compare options for outage monitoring to find your best fit.
Top EagleStatus Alternatives for 2025: Comprehensive Third-Party Monitoring Tools

Top EagleStatus Alternatives for 2025: Comprehensive Third-Party Monitoring Tools

Top 10 EagleStatus Alternatives for Comprehensive Monitoring
Centralizing Vendor Outage Data in Incident Management Platforms

Centralizing Vendor Outage Data in Incident Management Platforms

IsDown connects official data from vendor status pages to the most popular incident management tools
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