What is Docker current status?

Docker is currently operational. You can check Docker status and current incidents and outages on the top of the page. The status is updated in almost real-time, and you can see the issues affecting customers.

Is Docker down today?

Docker was not down today according to the official status page. In the last 24 hours, there were 0 outages reported. IsDown continuously monitors the Docker status page, looking for the latest outages and issues affecting customers. Check all recent outages in the section 'Latest Docker outages, issues and problems' at the top of the page.

When was the last Docker outage?

Docker last outage was on May 08, 2025 with the title "Docker Scout web dashboard not accessible to users"

How to monitor or check Docker status?

You can use IsDown service or go to Docker official status page. Some accounts also use Twitter to communicate the status.

How can I be notified when Docker is having issues?

You can create an account in IsDown and monitor multiple services or subscribe for updates on the official status page. IsDown will send you a notification in real-time when Docker has issues. Docker official status page might also offer notification options such as email, SMS, or Slack.

Is Docker Down? Check Docker status and current outages

Docker incident history

IsDown has tracked 72 incidents since started monitoring Docker downtimes in March 2022. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

May 08 2025

Docker Scout web dashboard not accessible to users

6 days ago · lasted about 3 hours

We are investigating issues with the Docker Scout web dashboard which are preventing access to the site.
May 08 2025

Testcontainers Cloud partially unavailable due to external infrastructure provider issues

6 days ago · lasted about 1 hour

Internal messaging platform timeouts connections
May 02 2025

Hub login not working

11 days ago · lasted 20 minutes

We are investigating the issue
Mar 2022 ...

IsDown started monitoring Docker status

We've tracked and collected 72 incidents since started monitoring Docker status

Docker user-reported issues in the last 24 hours

This chart displays the number of user-reported Docker problems 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.

Third-party monitoring

All Your Service Status Pages in One Dashboard

Monitoring 4000+ third-party services in real-time

Get custom alerts via Slack, Teams, Datadog, etc.

Create public or private status pages

Start Free Trial

14-day free trial · No credit card required

Trusted by thousands of teams

Monitor Docker and all your dependencies

Latest user comments about Docker issues

A

Arjun

9 days ago

Unable to login via docker login command
A

Andrei

Docker Hub Registry 16 days ago

net/http: TLS handshake timeout
R

Rick

Docker Hub Registry 3 months ago

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

3 months 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

Docker Hub Registry 3 months ago

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

Docker Hub Registry 3 months ago

python:3.11-slim-bullseye not able to pull
M

magy

Docker Hub Registry 3 months ago

cannot pull containers 500err
S

Sam

Docker Hub Registry 3 months ago

got 500 Internal Server Error
T

Tom

Docker Hub Registry 3 months ago

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

Jawad

Docker Hub Registry 3 months ago

Unable to pull and push images to docker.io recieving Internal server error 500
M

Milan

Docker Hub Registry 3 months ago

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

CHIHYU

Docker Hub Registry 3 months ago

500 error when pulling images
M

Mengz

Docker Hub Registry 3 months ago

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

Docker Hub Registry 3 months ago

Can't pull images, 500 error
S

Sukh

Docker Hub Registry 3 months ago

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

Alix

Docker Hub Registry 3 months ago

500 internal error on pull
H

hakima

Docker Hub Registry 3 months ago

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

3 months 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

Docker Hub Registry 3 months ago

No able to pull from DockerHub
V

Veaceslav

Docker Hub Registry 3 months ago

docker pull docker:latest returning 500 status code
I

Ivo

Docker Hub Registry 3 months ago

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

Aladin

Docker Hub Registry 3 months ago

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

martin

Docker Hub Registry 3 months ago

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

Ramon

3 months ago

Docker hub registry returning 500 errors
P

Patrick

Docker Hub Web 3 months ago

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

Adam

Docker Hub Registry 3 months ago

500 Internal Server Error
J

Johannes

Docker Hub Registry 3 months ago

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

Shobhit

Docker Hub Registry 3 months ago

Docker Hub is responding with ISE (500)
M

Madhusudan

Docker Hub Registry 3 months ago

giving 500 while pulling python image
B

bharat

Docker Hub Registry 3 months ago

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

Mykhailo

Docker Hub Registry 3 months ago

unexpected status code 500 Internal Server Error
J

JANOS

Docker Hub Registry 3 months ago

Cannot pull image from hub
R

Rio

Docker Hub Registry 3 months ago

We cannot build docker image
A

Andy

Docker Hub Registry 3 months ago

Getting HTTP req error code 500
T

Tobias

Docker Hub Registry 3 months ago

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

dom

Docker Hub Registry 3 months ago

500 Internal Server Error when pulling image
E

Eero

Docker Hub Registry 3 months ago

500 Internal Server Error
D

Denys

Docker Hub Registry 3 months ago

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

Lajos

Docker Hub Registry 3 months ago

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

Docker Hub Registry 3 months ago

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

Farhan

Docker Hub Registry 3 months ago

Dockerhub is down not able to pull images getting 500 error
K

Kamil

Docker Hub Registry 3 months ago

`500 Internal Server Error` on image download
T

tomer

Docker Hub Registry 3 months ago

get status 500 for pulling golang:1.21.3 image
R

RK

Docker Hub Registry 3 months ago

Not able to pull image, It is throwing 500
I

Igor

Docker Hub Registry 3 months ago

Failed to pull image "docker:20.10.6"
K

Kerenke

Docker Hub Registry 3 months ago

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

3 months ago

Can't pull images from the Docker registry.
A

Artyom

3 months 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

4 months 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

Docker Hub Registry 7 months ago

not accesible from where i am tested in my connection and outside
E

Erik

Docker Hub Registry 8 months ago

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

Doug

Docker Hub Registry 8 months ago

Personal Access Token authentication is broken
S

Sam

Docker Hub Registry 8 months ago

Website content not loading. 408 error
T

Terrence

8 months ago

Can't authenticate to use my PAID Docker account
M

Marco

Docker Hub Registry 8 months ago

I am pulling postgres:16 image and I am getting a 500 error
B

Benjamin

Docker Hub Registry 8 months ago

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

Tim

8 months ago

TLS timeout on arbitrary image pull
D

D

8 months ago

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

Aditya

Docker Hub Registry 9 months ago

Not able to download any docker image
A

Ari

9 months ago

Docker Desktop is stuck in starting mode

Docker outages in the last 30 days

Number of Incidents

6 issues

Last incident

6 days ago

Seamless Integrations

Get Docker outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.

Never miss an outage

Easy setup · No coding required

Works with your existing stack

Check Docker components, services, or regions current status in real-time

Docker Package Repositories

Docker Authentication

Docker Hub Web

Docker Hub Registry

Docker Hub Automated Builds

Docker.com Web

Docker Hub Security Scanning

Docker Docs

Docker Community Forums

Docker Support Site

Having problems with Docker? What can you do?

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.
Make a quick evaluation of the impact of the Docker outage
- 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.
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.
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.
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.
Did Docker recover?
- 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.
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.
- Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
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.

Related Services Dashboard

Services commonly monitored together with Docker

Create your own dashboard

GitHub

AWS

Slack

Google Workspace

Jira Software

Cloudflare

MINOR

Google Cloud

Zoom

Datadog US1

Azure

Microsoft 365

Confluence

Zendesk

Okta

Microsoft Office 365

Want to be 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.