Check if Docker Hub Registry is down, recent outages, user-reported issues, and outages map.
Docker Hub Registry is working normally
Last checked from Docker's status page
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.
IsDown has tracked 24 incidents for Docker Hub Registry since started monitoring Docker status in March 2022. We collect data from 4400+ services, and normalize the data to give you a clear picture of the impact of the outage.
9 days ago · lasted 5 days
Due to a third-party vendor outage, users from the India area might experience increased latency when pulling images.
10 days ago · lasted about 11 hours
We are experiencing increased latency for pulling images because of a third-party vendor outage. Users in India area might be impacted.
11 days ago · lasted 24 minutes
A few users reported issues when deleting repositories, we are investigating this issue
We've tracked and collected 24 incidents for Docker Hub Registry since started monitoring Docker status
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
daniele
not able to pull and push images
Andrei
net/http: TLS handshake timeout
Rick
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...
Francesco
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...
Pratham
python:3.11-slim-bullseye not able to pull
magy
cannot pull containers 500err
Sam
got 500 Internal Server Error
Tom
Docker Hub servers report http 500 errors when pulling images.
Jawad
Unable to pull and push images to docker.io recieving Internal server error 500
Milan
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error (manager.go:254:7s)
CHIHYU
500 error when pulling images
Mengz
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...
Ozan
Can't pull images, 500 error
Sukh
Meanwhile Docker Hub is down, use Google's mirror for now: "registry-mirrors": ["https://mirror.gcr.io"]
Alix
500 internal error on pull
hakima
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
Han
No able to pull from DockerHub
Veaceslav
docker pull docker:latest returning 500 status code
Ivo
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Aladin
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
martin
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Adam
500 Internal Server Error
Johannes
error pulling image download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Shobhit
Docker Hub is responding with ISE (500)
Madhusudan
giving 500 while pulling python image
bharat
docker is down error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Mykhailo
unexpected status code 500 Internal Server Error
JANOS
Cannot pull image from hub
Rio
We cannot build docker image
Andy
Getting HTTP req error code 500
Tobias
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
dom
500 Internal Server Error when pulling image
Eero
500 Internal Server Error
Denys
error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Lajos
failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/mariadb/blobs/sha256:d045ae11ce7ea8529ff420da5b7f4f19302c0824db2b81be3fed1a2ca8c4e639: 500 Internal Server Error
Paul
Getting 500 internal server error trying to pull otel/opentelemetry-collector-contrib:latest
Farhan
Dockerhub is down not able to pull images getting 500 error
Kamil
`500 Internal Server Error` on image download
tomer
get status 500 for pulling golang:1.21.3 image
RK
Not able to pull image, It is throwing 500
Igor
Failed to pull image "docker:20.10.6"
Kerenke
I can't pull images getting error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error`
isaac
not accesible from where i am tested in my connection and outside
Erik
Error response from daemon: Get "https://registry-1.docker.io/v2/": unauthorized: incorrect username or password
Doug
Personal Access Token authentication is broken
Sam
Website content not loading. 408 error
Marco
I am pulling postgres:16 image and I am getting a 500 error
Benjamin
Cant pull images with TLS handshake timeout. Docker hub page also not loading
Aditya
Not able to download any docker image
Kaustubh
I cannot sign in in docker hub registry
Edwin
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.
leonardo
error pulling image configuration: download failed after attempts=6: dial tcp: lookup production.cloudflare.docker.com on 127.0.0.53:53: read udp 127.0.0.1:50252->127.0.0.53:53: i/o timeout
Francisco
Error response from daemon: Head "https://registry-1.docker.io/v2/library/nginx/manifests/latest": received unexpected HTTP status: 503 Service Unavailable
Mick
https://auth.docker.io/token: 503 Service Unavailable
Estren
Can't login and Build images
Alferez
received unexpected HTTP status: 503 Service Unavailable
George
It looks like Docker hub is down, I cant build any Dockerfiles using online images
Igor
Received: "HTTP status: 503 Service Unavailable" on docker pull
Jonas
https://auth.docker.io returns a 503
Jonathan
503 Service Unavailable while trying to pull an image in Azure Pipelines
Stay Ahead of Docker Outages
IsDown aggregates various status pages from services into a very clear dashboard. Worth every penny.
Services commonly monitored together with Docker
Docker Hub Registry isn't down. You can check Docker Hub Registry status and incident details on the top of the page. IsDown continuously monitors Docker Hub Registry official status page every few minutes. In the last 24 hours, there were 0 outages reported.
Docker Hub Registry is currently operational. You can check Docker Hub Registry 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 Hub Registry being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the Docker Hub Registry 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 Hub Registry last outage was on July 31, 2025 with the title "Monitoring issues with pulls in India"
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.
IsDown offers an easy way to monitor Docker with maximum flexibility
IsDown monitors Docker Hub Registry for major outages. A major outage is when Docker Hub Registry 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 Hub Registry 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
