Docker Hub Registry is operational
Updated
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.
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.
Rick
about 2 months agoCan´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
about 2 months agoFailed 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
about 2 months agopython:3.11-slim-bullseye not able to pull
magy
about 2 months agocannot pull containers 500err
Sam
about 2 months agogot 500 Internal Server Error
Tom
about 2 months agoDocker Hub servers report http 500 errors when pulling images.
Jawad
about 2 months agoUnable to pull and push images to docker.io recieving Internal server error 500
Milan
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error (manager.go:254:7s)
CHIHYU
about 2 months ago500 error when pulling images
Mengz
about 2 months agoFailed 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
about 2 months agoCan't pull images, 500 error
Sukh
about 2 months agoMeanwhile Docker Hub is down, use Google's mirror for now: "registry-mirrors": ["https://mirror.gcr.io"]
Alix
about 2 months ago500 internal error on pull
hakima
about 2 months agolatest: 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
about 2 months agoNo able to pull from DockerHub
Veaceslav
about 2 months agodocker pull docker:latest returning 500 status code
Ivo
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Aladin
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
martin
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Adam
about 2 months ago500 Internal Server Error
Johannes
about 2 months agoerror pulling image download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Shobhit
about 2 months agoDocker Hub is responding with ISE (500)
Madhusudan
about 2 months agogiving 500 while pulling python image
bharat
about 2 months agodocker is down error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Mykhailo
about 2 months agounexpected status code 500 Internal Server Error
JANOS
about 2 months agoCannot pull image from hub
Rio
about 2 months agoWe cannot build docker image
Andy
about 2 months agoGetting HTTP req error code 500
Tobias
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
dom
about 2 months ago500 Internal Server Error when pulling image
Eero
about 2 months ago500 Internal Server Error
Denys
about 2 months agoerror pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error
Lajos
about 2 months agofailed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/mariadb/blobs/sha256:d045ae11ce7ea8529ff420da5b7f4f19302c0824db2b81be3fed1a2ca8c4e639: 500 Internal Server Error
Paul
about 2 months agoGetting 500 internal server error trying to pull otel/opentelemetry-collector-contrib:latest
Farhan
about 2 months agoDockerhub is down not able to pull images getting 500 error
Kamil
about 2 months ago`500 Internal Server Error` on image download
tomer
about 2 months agoget status 500 for pulling golang:1.21.3 image
RK
about 2 months agoNot able to pull image, It is throwing 500
Igor
about 2 months agoFailed to pull image "docker:20.10.6"
Kerenke
about 2 months agoI can't pull images getting error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error`
isaac
5 months agonot accesible from where i am tested in my connection and outside
Erik
6 months agoError response from daemon: Get "https://registry-1.docker.io/v2/": unauthorized: incorrect username or password
Doug
6 months agoPersonal Access Token authentication is broken
Sam
6 months agoWebsite content not loading. 408 error
Marco
7 months agoI am pulling postgres:16 image and I am getting a 500 error
Benjamin
7 months agoCant pull images with TLS handshake timeout. Docker hub page also not loading
Aditya
7 months agoNot able to download any docker image
Kaustubh
7 months agoI cannot sign in in docker hub registry
Edwin
8 months agoSomething 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
8 months agoerror 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
10 months agoError response from daemon: Head "https://registry-1.docker.io/v2/library/nginx/manifests/latest": received unexpected HTTP status: 503 Service Unavailable
Mick
10 months agohttps://auth.docker.io/token: 503 Service Unavailable
Estren
10 months agoCan't login and Build images
Alferez
10 months agoreceived unexpected HTTP status: 503 Service Unavailable
George
10 months agoIt looks like Docker hub is down, I cant build any Dockerfiles using online images
Igor
10 months agoReceived: "HTTP status: 503 Service Unavailable" on docker pull
Jonas
10 months agohttps://auth.docker.io returns a 503
Jonathan
10 months ago503 Service Unavailable while trying to pull an image in Azure Pipelines
Brandon
10 months agoError response from daemon: Head "https://registry-1.docker.io/v2/lissy93/dashy/manifests/latest": received unexpected HTTP status: 503 Service Unavailable
Pablo
10 months agoNot being able to pull images from CI
IsDown has tracked 19 incidents for Docker Hub Registry since started monitoring Docker status in March 2022.
about 2 months ago · lasted 24 minutes
We are investigating an issue with customers and users not able to pull images from Docker Hub. ``` > error pulling image configuration: download failed after attempts=6: received unexpected HTTP status: 500 Internal Server Error ``` This ... More details
4 months ago · lasted about 2 hours
Some images in the following repositories can fail to be pulled with a `not found: manifest unknown` error api-firewall arangodb bash crate docker drupal friendica ghost haproxy irssi julia matomo openjdk rabbitmq redmine ruby ... More details
5 months ago · lasted about 2 hours
Users are experiencing delays and timeouts when attempting to use access tokens. More details
We've tracked and collected 19 incidents for Docker Hub Registry since started monitoring Docker status
1 incident in 2025
Number of Incidents
0 issues
Last incident
57 days ago
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.
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.
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 February 06, 2025 with the title "Pulling images from Docker Hub fails with 500 errors"
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.
14-day free trial · No credit card required · No code required