Skip to main content
Docker Hub logo

Is Docker Hub Down?

No — Docker Hub is up

Reachable from all 8 checked regions

Average response time: 425ms

Last checked · checks run every 6 hours

Official status page: https://www.dockerstatus.com

Docker Hub uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
296ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 24 checks
Aug 5: 100.00% uptime, 28 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 38 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 24 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
162ms
DNS 0ms TCP 1ms TLS 16ms TTFB 149ms
arn
166ms
DNS 0ms TCP 1ms TLS 11ms TTFB 151ms
bom
309ms
DNS 1ms TCP 3ms TLS 17ms TTFB 282ms
cdg
132ms
DNS 0ms TCP 1ms TLS 9ms TTFB 120ms
dfw
416ms
DNS 0ms TCP 1ms TLS 13ms TTFB 326ms
ewr
704ms
DNS 0ms TCP 1ms TLS 9ms TTFB 685ms
fra
1428ms
DNS 0ms TCP 1ms TLS 13ms TTFB 1411ms
syd
465ms
DNS 0ms TCP 1ms TLS 15ms TTFB 256ms
yyz
83ms
DNS 0ms TCP 2ms TLS 9ms TTFB 68ms

What Docker Hub does

Docker Hub is the default container image registry, hosting both official base images and private repositories. Build pipelines and Kubernetes clusters pull from it by default, so an outage does not merely block developers browsing for images: it stops deployments and prevents nodes from starting any container they do not already hold in a local cache.

What an outage looks like

docker pull fails with authentication errors or times out partway through a layer download. CI builds break at the FROM line before running a single step of your own. Kubernetes pods sit in ImagePullBackOff and never start. Machines holding the image already keep running untouched, so failures appear first on new deployments, scale-ups and fresh nodes.

What to do about it

Check dockerstatus.com, which lists Docker Hub Registry and Docker Authentication as separate components; anonymous pulls of public images sometimes succeed while logins fail. Anything already cached locally keeps running, so postpone rolling restarts and node replacements until it recovers. A pull-through cache or a mirrored registry removes this dependency next time.

Is it down for everyone, or just you?

If this page says Docker Hub is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
GitLab
GitLab
AWS
AWS
Fly.io
Fly.io

Docker Hub outage FAQ

Is Docker Hub down or have I hit the rate limit?
They look similar but read differently. A rate limit returns an explicit toomanyrequests error naming the pull limit, while an outage gives timeouts, 500-class errors or authentication failures. Rate limits also apply per account or IP, so a colleague on a different network pulling successfully points at limits rather than an outage. Check dockerstatus.com to separate the two.
Will my running containers stop if Docker Hub goes down?
No. Containers already running hold their image locally and are unaffected by the registry being unreachable. The risk is anything that triggers a fresh pull: a deployment, a scale-up, a node replacement, or a restart policy that pulls before starting. This is why avoiding rolling restarts during a registry incident matters more than it first appears.
How do I keep deploying during a Docker Hub outage?
Deploy images that are already cached on the target nodes, or pull from a mirror if you run one. Some registries can serve as a pull-through cache for Docker Hub, holding copies of images you have fetched before. Without one, the practical answer during the incident is to pause deployments rather than to work around the registry.
Does a Docker Hub outage affect private and public images equally?
Not always. Private images require an authenticated pull, so an incident affecting Docker Authentication breaks them while anonymous pulls of public images continue to work. The status page reports the registry and authentication separately for this reason. If public base images pull fine but yours do not, authentication is the likely component.
Why do my Kubernetes pods show ImagePullBackOff?
The kubelet tried to fetch the image, failed, and is backing off before retrying. During a registry outage this is the normal symptom for any pod scheduled onto a node without a cached copy. Pods usually recover on their own once pulls succeed again, since the backoff keeps retrying, so deleting and recreating them rarely helps.

How we measure this

  • We request Docker Hub's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Docker Hub publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Docker Hub goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required