Package registries
Is Docker Hub down?
Live Docker Hub status, measured independently. We probe 6 Docker Hub endpoints from monitoring regions on every continent and record every outage we detect.
Docker Hub is up
Our probes are reaching Docker Hub normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 173 to 471 msUnknownp50median response288 msp95slowest 5% of checks801 ms500 ms250024 h ago12 h agonow
- Hub API100% uptime, 30 days6 regions, 134 to 313 msUnknownp50median response231 msp95slowest 5% of checks259 ms500 ms250024 h ago12 h agonow
- Registry100% uptime, 30 days6 regions, 188 to 808 msUnknownp50median response514 msp95slowest 5% of checks761 ms1000 ms500024 h ago12 h agonow
- Auth service99.99% uptime, 30 days6 regions, 195 to 497 msUnknownp50median response314 msp95slowest 5% of checks480 ms500 ms250024 h ago12 h agonow
- Documentation100% uptime, 30 days6 regions, 82 to 510 msUnknownp50median response203 msp95slowest 5% of checks357 ms500 ms250024 h ago12 h agonow
- Official status feed100% uptime, 30 days6 regions, 198 to 616 msUnknownp50median response432 msp95slowest 5% of checks678 ms1000 ms500024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Docker Hub goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Docker Hub goes down. They don't count against your monitor quota. Free plan, no card required.
About Docker Hub outages
Docker Hub is the default registry for container images, so a Docker Hub incident breaks docker pull, CI jobs that use public base images, and Kubernetes pods that need to pull on restart. Rate limiting for anonymous pulls adds a second failure mode that looks similar.
Image pulls go through registry-1.docker.io and auth.docker.io, not hub.docker.com. We probe all three, plus the Hub API and the documentation, so a website incident is not mistaken for a registry outage.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website hub.docker.com is unreachable. Browsing images is affected; pulls may still work. | httphub.docker.com | HTTP 200 | 1 min |
Hub API The Docker Hub API is failing. Tag listings and automated tooling break. | httphub.docker.com/v2/repositories/library/alpine/tags | HTTP 200 | 2 min |
Registry The image registry is not answering with its normal authentication challenge. docker pull fails. | httpregistry-1.docker.io/v2/ | HTTP 401 | 1 min |
Auth service Anonymous pull tokens cannot be issued. Pulls fail even if the registry itself is up. | httpauth.docker.io/token | HTTP 200 | 2 min |
Documentation Docker's documentation is unreachable. | httpdocs.docker.com | HTTP 200 | 5 min |
Official status feed Docker's status page is unreachable. | httpwww.dockerstatus.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Docker's official status page.
Recent Docker Hub outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Docker Hub is up. Is your Docker Hub integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Docker Hub and fail quietly. Here is what teams that rely on Docker Hub monitor on their side.
Pods and jobs that pull images at start
A Kubernetes node that cannot pull an image leaves pods in ImagePullBackOff. Heartbeats on jobs and probes on services surface it before customers do.
Heartbeat monitoringYour private registry or pull-through cache
If you mirror images in GHCR, ECR, or a registry proxy, monitor it explicitly.
HTTP monitoringDocker Hub status: frequently asked questions
No. That is Docker Hub's anonymous pull rate limit, which is enforced per IP address. Authenticate pulls or use a pull-through cache. Our probes stay green during rate limiting because the registry is answering correctly.
Look at the per-region results above. If our probes fail from every region, Docker Hub has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Docker Hub may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Docker Hub" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Docker Hub: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other package registries
upti.my is not affiliated with Docker Hub. Docker Hub and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.