Docker Hub Registry Status - Is Docker Hub Registry Down?

Docker Hub Registry is operational

Updated

Docker Hub Registry not working for you?

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 Hub Registry 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 Hub Registry problems

  • A

    Andrei

    net/http: TLS handshake timeout

  • R

    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...

  • F

    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...

  • P

    Pratham

    python:3.11-slim-bullseye not able to pull

  • M

    magy

    cannot pull containers 500err

  • S

    Sam

    got 500 Internal Server Error

  • T

    Tom

    Docker Hub servers report http 500 errors when pulling images.

  • J

    Jawad

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

  • M

    Milan

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

  • C

    CHIHYU

    500 error when pulling images

  • M

    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...

  • O

    Ozan

    Can't pull images, 500 error

  • S

    Sukh

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

  • A

    Alix

    500 internal error on pull

  • H

    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

  • H

    Han

    No able to pull from DockerHub

  • V

    Veaceslav

    docker pull docker:latest returning 500 status code

  • I

    Ivo

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

  • A

    Aladin

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

  • M

    martin

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

  • A

    Adam

    500 Internal Server Error

  • J

    Johannes

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

  • S

    Shobhit

    Docker Hub is responding with ISE (500)

  • M

    Madhusudan

    giving 500 while pulling python image

  • B

    bharat

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

  • M

    Mykhailo

    unexpected status code 500 Internal Server Error

  • J

    JANOS

    Cannot pull image from hub

  • R

    Rio

    We cannot build docker image

  • A

    Andy

    Getting HTTP req error code 500

  • T

    Tobias

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

  • D

    dom

    500 Internal Server Error when pulling image

  • E

    Eero

    500 Internal Server Error

  • D

    Denys

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

  • L

    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

  • P

    Paul

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

  • F

    Farhan

    Dockerhub is down not able to pull images getting 500 error

  • K

    Kamil

    `500 Internal Server Error` on image download

  • T

    tomer

    get status 500 for pulling golang:1.21.3 image

  • R

    RK

    Not able to pull image, It is throwing 500

  • I

    Igor

    Failed to pull image "docker:20.10.6"

  • K

    Kerenke

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

  • I

    isaac

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

  • E

    Erik

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

  • D

    Doug

    Personal Access Token authentication is broken

  • S

    Sam

    Website content not loading. 408 error

  • M

    Marco

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

  • B

    Benjamin

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

  • A

    Aditya

    Not able to download any docker image

  • K

    Kaustubh

    I cannot sign in in docker hub registry

  • E

    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.

  • L

    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

  • F

    Francisco

    Error response from daemon: Head "https://registry-1.docker.io/v2/library/nginx/manifests/latest": received unexpected HTTP status: 503 Service Unavailable

  • M

    Mick

    https://auth.docker.io/token: 503 Service Unavailable

  • E

    Estren

    Can't login and Build images

  • A

    Alferez

    received unexpected HTTP status: 503 Service Unavailable

  • G

    George

    It looks like Docker hub is down, I cant build any Dockerfiles using online images

  • I

    Igor

    Received: "HTTP status: 503 Service Unavailable" on docker pull

  • J

    Jonas

    https://auth.docker.io returns a 503

  • J

    Jonathan

    503 Service Unavailable while trying to pull an image in Azure Pipelines

  • B

    Brandon

    Error response from daemon: Head "https://registry-1.docker.io/v2/lissy93/dashy/manifests/latest": received unexpected HTTP status: 503 Service Unavailable

Be the first to know when Docker and other third-party services go down

Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.

Start Monitoring Your Vendors 14-day free trial · No credit card required · No setup required - just add your vendors

Docker Hub Registry outage history

IsDown has tracked 19 incidents for Docker Hub Registry since started monitoring Docker status in March 2022.

  • Feb 06 2025
    Pulling images from Docker Hub fails with 500 errors

    3 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

  • Dec 14 2024

    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

  • Nov 13 2024
    Personal access tokens: delays and timeout

    6 months ago · lasted about 2 hours

    Users are experiencing delays and timeouts when attempting to use access tokens. More details

  • Mar 2022 ...
    IsDown started monitoring Docker status

    We've tracked and collected 19 incidents for Docker Hub Registry since started monitoring Docker status

Sign up and check all outage history

Having problems with Docker Hub Registry? What can you do?

  1. First, stay calm.

    • We know it's stressful when Docker Hub Registry 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 Hub Registry already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Docker Hub Registry 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 Hub Registry 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 aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.

Be the first to know when Docker is down (and all your dependencies)

Instant Outage Alerts

Get notified on Slack, Datadog, Incident.io and more

Unified Dashboard

Monitor all vendors status in one place

Status Pages

Create private or public status pages

Historical Data

Track uptime over time in all your vendors

Start Monitoring your Vendors
14-day free trial No credit card required
Learn more about IsDown

Docker Hub Registry is part of Docker. Check the Docker's status.

1 incident in 2025

Docker Hub Registry outages in the last 30 days

Number of Incidents

0 issues

Last incident

84 days ago

Companies that monitor Docker also follow the status of these services

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

Why teams choose IsDown:

  • ✓ Real-time alerts for Docker and 3850+ cloud services
  • ✓ Unified dashboard for all your vendors
  • ✓ Custom status pages for your team

14-day free trial • No credit card required

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 Monitoring Your Vendors 14-day free trial · No credit card required · No setup required - just add your vendors

Frequently Asked Questions

Is Docker Hub Registry down today?

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 2 outages reported.

What is the current Docker Hub Registry status?

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.

Is there a Docker Hub Registry 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 Hub Registry slow today?

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.

How are Docker Hub Registry outages detected?

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.

When was the last Docker Hub Registry outage?

Docker Hub Registry last outage was on February 06, 2025 with the title "Pulling images from Docker Hub fails with 500 errors"

Docker not working for you? How do I know if Docker is down?

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.

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 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.

Minor Outages 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.

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.

Latest Articles from our Blog

How Often Has GitHub Gone Down? A Data-Backed Look at 2024 Outages

How Often Has GitHub Gone Down? A Data-Backed Look at 2024 Outages

Check out GitHub outage trends in 2024. Explore the frequency of degraded performance across GitHub services. Learn strategies to mitigate downtime risks.

Is Github Reliable? Outage Trends, Stats & Comparisons

Is Github Reliable? Outage Trends, Stats & Comparisons

Is GitHub reliable for critical workflows? Explore outage trends, uptime data, and how it compares to GitLab and Bitbucket in real-world performance.
What Is a Status Page Aggregator?

What Is a Status Page Aggregator?

Discover how a status page aggregator simplifies monitoring third-party services, delivers real-time alerts, and helps businesses prevent costly downtime.
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