Is Docker Hub down right now?

No. Our checks are finding no problems with Docker Hub right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Docker Hub continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't connect, can't log in, API errors, downloads failing, upload failing, search not working and no response / timing out. Those are the options the report button offers for Docker Hub, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Docker Hub specifically, the registry, the authentication service and the website are separate, and image layers come from a CDN. The website can load perfectly while pulls fail, and one unhealthy CDN edge affects your region while others pull normally. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Docker Hub, run docker pull hello-world from a different network. Succeeding there while your own image fails points at that repository, its tag or your credentials. Failing everywhere while another registry works separates Docker Hub from your machine's DNS and proxy. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Docker Hub's side. Specifically: check whether you are rate limited rather than down. Anonymous pulls are capped per IP address, and a shared office or CI egress address burns the allowance quickly, which returns an error that reads as an outage. Images already in your local cache keep running. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Docker Hub does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe docker.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Docker Hub says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at www.dockerstatus.com, and it is linked further up this page. That is Docker Hub's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Docker Hub or docker.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Docker Hub's own support, not us.