Protego field desk

LIVE STATUS CHECKER

Is Docker Hub down right now?

Latest check: Docker Hub is up. See the live result and check time below

docker pull timing out, builds failing in CI or hub.docker.com not loading? Countless build pipelines pull base images from Docker Hub. We check the registry, registry sign-in and the Hub website every minute, read dockerstatus.com and count reports from other developers.

Registry + sign-inHub websiteOfficial Docker statusFree, no sign-in
LIVE STATUS: UP

Docker Hub is up

  • Every check passed and user reports are at normal levels

Checked

Next refresh in 60s

STEP 1: FREE TROUBLESHOOTER

Why isn't Docker Hub working for you?

Six checks on your own device in about ten seconds: your connection, whether your network blocks Docker Hub, your DNS, your device clock, cookies and your network. You get the exact fix for what we find.

STEP 2

Report a problem

What is not working for you? One tap, no sign-in. Your report helps everyone else see what is happening.

One report per person, checked for duplicates and abuse. We store the problem type, your country and anonymous codes that change daily. Never your IP address, name or account.

User reports in the last 24 hours

0 reports, 0 in the last 15 minutes from 0 networks

24 hours ago12 hours agoNow

No one has reported a Docker Hub problem here in the last 24 hours. Having trouble? Be the first to report it above.

What we checked, right now

Live requests from our servers to the Docker Hub registry, registry sign-in, hub.docker.com, Docker account sign-in and the docs, refreshed every minute.

Docker Hub endpoints

  • Registry

    registry-1.docker.io (docker pull and push)

    OK: 28 ms
  • Registry sign-in

    auth.docker.io (tokens for pulls)

    OK: 52 ms
  • Docker Hub website

    hub.docker.com

    OK: 75 ms
  • Docker account sign-in

    login.docker.com

    OK: 48 ms
  • Docker docs

    docs.docker.com

    OK: 55 ms

DNS: can the internet find Docker Hub?

  • Cloudflare DNS (1.1.1.1)

    Can the internet find registry-1.docker.io?

    OK: 14 ms
  • Google DNS (8.8.8.8)

    A second, independent resolver

    OK: 13 ms
  • Docker's own nameservers

    Answer for docker.io even if public DNS fails

    OK: 34 ms

Docker official status

No known issues on dockerstatus.com for the Docker Hub registry, Hub website, authentication or package repositories.

Source: dockerstatus.com.

Docker Hub registry response time, last 24 hours

24 hours agoPeak 1000 msNow
№ 01

Is Docker Hub down or is it just me? Quick checks

  1. 1

    Read the live status above.

    The registry, which docker pull uses, can fail while hub.docker.com loads, and the other way round.

  2. 2

    Check for rate limits.

    Docker Hub limits how many images you can pull, especially without signing in. "toomanyrequests" is a limit, not an outage.

  3. 3

    Sign in.

    Run docker login. Signed-in pulls get higher limits and are more reliable from shared CI runners.

  4. 4

    Test DNS and your proxy.

    Corporate proxies and firewalls often block registry-1.docker.io or the storage servers images download from.

  5. 5

    Try a mirror.

    If you use a registry mirror or cache, pull through it; it may already hold the image.

№ 02

Docker Hub error messages and what they mean

ErrorWhat it meansWhat to do
toomanyrequests: You have reached your pull rate limitYou used up your pull allowanceNot an outage: run docker login, or use a mirror or cache
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceledYour machine could not reach the registry in timeCheck the registry above; if green, check your network, proxy and DNS
received unexpected HTTP status: 500 or 503Docker Hub could not serve the requestRetry later; check the official status above
unauthorized: authentication requiredThe image is private or your login expiredNot an outage: run docker login again or check access to the repository
manifest unknown / not foundThat image or tag does not existNot an outage: check the image name and tag
№ 03

Keep builds working when Docker Hub is down

  • Cache base images. Use a pull-through cache or mirror in your own registry so builds do not depend on Docker Hub every time.

  • Pin images by digest. A digest pins the exact image, so a cached copy is always valid and builds are reproducible.

  • Sign in on CI runners. Anonymous pulls from shared runners hit rate limits quickly and look like outages.

  • Scan what you pull. Cached and mirrored images still need vulnerability scanning and a hardened Dockerfile.

№ 04

Why does Docker Hub go down?

Cloud provider outages
In October 2025 an AWS outage in US-East-1 caused a complete Docker Hub outage for several hours.
Registry and storage problems
Pulls depend on the registry, the sign-in service and the storage servers that hold image layers; any one failing breaks docker pull.
Rate limits
Pull limits make busy shared CI runners fail even when Docker Hub is healthy.
Network problems
Proxies, firewalls and DNS issues on your side cause most "registry unreachable" errors.
№ 05

Docker Hub outage history

The biggest Docker Hub incidents and what caused them. Durations are approximate and come from public reporting and official reviews.

  • OCT 20, 2025

    Complete outage of Docker Hub and related services from 08:01 UTC, partly restored from 09:40 UTC and fully restored on Oct 21 at 09:42 UTC

    A widespread AWS outage in the US-East-1 region. Source: Docker incident report

№ 06

How this page works

Every minute our servers request Docker Hub's main endpoints, resolve registry-1.docker.io through Cloudflare, Google and docker's own nameservers, and read dockerstatus.com. We combine that with one-tap user reports, filtered for duplicates and abuse: a spike needs at least 12 reports in 15 minutes from 8 or more different networks.

Built to avoid false alarms: a failed request is retried before it counts, a single bad check never says "down" on its own, and a check that fails for reasons on our side is shown as inconclusive rather than as an outage. Limits: we check from one location, so a regional problem may first show up in user reports. Reports store only the problem type, a country code and anonymous codes that change daily; never your IP address. Protego is independent and not affiliated with Docker Hub. Last reviewed .

№ 07

Frequently asked questions

Is Docker Hub down today or is it just me?

Compare two signals on this page. Our live check shows whether the Docker Hub registry answers from our servers, and the user-reports chart shows whether other developers are reporting problems right now. If both look fine, check rate limits, your login, your proxy and DNS.

Is Docker Hub down right now?

The status box at the top of this page answers that live. We check the registry, registry sign-in and hub.docker.com every minute, read dockerstatus.com and count user reports.

Why does docker pull say "toomanyrequests"?

You reached Docker Hub’s pull rate limit. It is not an outage. Sign in with docker login, or pull through a mirror or cache.

Is Docker Hub down because AWS is down?

Sometimes. Docker Hub runs on AWS, and the October 2025 AWS US-East-1 outage took Docker Hub down completely. See our AWS status page.

Where does Docker post outages?

On dockerstatus.com, with separate entries for the Hub registry, Hub website, authentication and other Docker products. We show it live on this page.

FOR DEVOPS ENGINEERS

Harden your Dockerfiles

Our free Dockerfile linter flags running as root, unpinned base images, leaked secrets and other risky patterns, entirely in your browser.

Lint a Dockerfile free

IS IT DOWN?

Check other services