Check if Docker is down, recent outages, user-reported issues, and outages map.
Docker is working normally
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. Sign up for free to see more Docker status data.
IsDown has tracked 94 incidents since started monitoring Docker status in March 2022. We collect data from 4522+ services, and normalize the data to give you a clear picture of the impact of the outage.
| Date | Status | Incident | Duration |
|---|---|---|---|
|
Oct 09, 2025
11:19 AM EDT
|
Minor | DHI customization builds backed up | about 1 hour |
|
Sep 29, 2025
01:26 PM EDT
|
Major | Docs Site is down | 28 minutes |
|
Sep 24, 2025
07:11 PM EDT
|
Minor | Issues authenticating with Docker Hub | about 2 hours |
|
Sep 03, 2025
06:52 AM EDT
|
Minor | Intermitent login issues | about 1 hour |
|
Aug 20, 2025
11:24 AM EDT
|
Major | Testcontainers Cloud and Docker Offload Availability | 4 minutes |
|
Aug 19, 2025
11:41 AM EDT
|
Minor | Hub UI down | 12 minutes |
|
Aug 14, 2025
09:49 PM EDT
|
Minor | Increased Errors from Docker Offload | 28 minutes |
|
Jul 31, 2025
11:37 AM EDT
|
Minor | Monitoring issues with pulls in India | 5 days |
|
Jul 30, 2025
09:19 AM EDT
|
Minor | Monitoring issues with pulls in India | about 11 hours |
|
Jul 29, 2025
08:28 AM EDT
|
Minor | Users reporting issues with deleting repositories | 24 minutes |
I'm not able to pull docker images, and also, when navigating to the image documentation page on docker hub, I noticed that the documentation did not load, and instead, an error is being displayed to the UI.
Cannot pull public images
Failing to pull public images, like https://hub.docker.com/_/debian Authentication error
Docker Hub out, log error: failed to solve: node:18-alpine: failed to resolve source metadata for docker.io/library/node:18-alpine: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/node/manifests/18-alpine: 401 Unauthorized
Having trouble authenticating my login to Docker Desktop on windows and cant pull containers
not able to pull and push images
Unable to login via docker login command
net/http: TLS handshake timeout
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...
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
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...
python:3.11-slim-bullseye not able to pull
cannot pull containers 500err
got 500 Internal Server Error
Docker Hub servers report http 500 errors when pulling images.
Unable to pull and push images to docker.io recieving Internal server error 500
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error (manager.go:254:7s)
500 error when pulling images
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...
Can't pull images, 500 error
Meanwhile Docker Hub is down, use Google's mirror for now: "registry-mirrors": ["https://mirror.gcr.io"]
500 internal error on pull
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
ERROR: Job failed: failed to pull image "docker:dind" with specified policies [always]: error pulling image configuration: download failed after attempts=6
No able to pull from DockerHub
docker pull docker:latest returning 500 status code
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Docker hub registry returning 500 errors
Can't pull images: error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
500 Internal Server Error
error pulling image download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Docker Hub is responding with ISE (500)
giving 500 while pulling python image
docker is down error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
unexpected status code 500 Internal Server Error
Cannot pull image from hub
We cannot build docker image
Getting HTTP req error code 500
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
500 Internal Server Error when pulling image
500 Internal Server Error
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/mariadb/blobs/sha256:d045ae11ce7ea8529ff420da5b7f4f19302c0824db2b81be3fed1a2ca8c4e639: 500 Internal Server Error
Getting 500 internal server error trying to pull otel/opentelemetry-collector-contrib:latest
Dockerhub is down not able to pull images getting 500 error
`500 Internal Server Error` on image download
get status 500 for pulling golang:1.21.3 image
Not able to pull image, It is throwing 500
Failed to pull image "docker:20.10.6"
I can't pull images getting error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error`
Can't pull images from the Docker registry.
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...
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.
not accesible from where i am tested in my connection and outside
Error response from daemon: Get "https://registry-1.docker.io/v2/": unauthorized: incorrect username or password
Personal Access Token authentication is broken
Website content not loading. 408 error
Can't authenticate to use my PAID Docker account
| Component | Status |
|---|---|
| Docker Package Repositories | OK |
| Docker Authentication | OK |
| Docker Hub Web | OK |
| Docker Hub Registry | OK |
| Docker Hub Automated Builds | OK |
| Docker.com Web | OK |
| Docker Hub Security Scanning | OK |
| Docker Docs | OK |
| Docker Community Forums | OK |
| Docker Support Site | OK |
Services commonly monitored together with Docker and alternatives
GitHub
AWS
Slack
Google Workspace
Jira Software
Cloudflare
Google Cloud
Zoom
Datadog US1
Microsoft Azure
Microsoft 365
Confluence
Zendesk
Okta
Microsoft Office 365
Docker is a platform for developing, shipping, and running applications inside lightweight, portable containers, with services for image storage, automated builds, and security scanning.
Monitoring Docker since March 2022
Tracking 10 Docker services and regions
39 incidents in 2025
Number of Incidents
3 issues
Last incident
3 days ago
Be the first to know when Docker goes down
Monitor All your Vendors in One Place
4522+ third-party services available to monitor
Know Before They Know
Alerts 30+ minutes before official updates
Stop the Ticket Flood
Cut "is it down?" tickets by 80%
IsDown aggregates various status pages from services into a very clear dashboard. Worth every penny.
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.
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.
No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.
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.
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.
Docker last outage was on October 09, 2025 with the title "DHI customization builds backed up"
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.
IsDown and DownDetector help users determine if Docker 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 instead of just relying on reports from users. The integration allows us to provide more details about Docker's Outages, 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.
IsDown offers an easy way to monitor Docker with maximum flexibility
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.
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.
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.
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.
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.
14-day free trial · No credit card required · No code required
