Is Docker Hub down?

Understanding Docker Hub availability

Docker Hub availability includes more than the website at hub.docker.com. A disruption may affect repository browsing, authentication, or image pulls independently. Therefore, one failed login or image pull does not by itself prove that Docker Hub is experiencing a platform-wide outage.

Check the official Docker status page for reported incidents and degraded service. If no incident is listed, compare browser access with Docker client behavior and, when possible, test from another network. These comparisons help separate a Docker Hub incident from an account, repository, image-reference, DNS, proxy, firewall, certificate, or local Docker configuration problem.

The exact error is useful evidence:

• Authentication or permission messages usually point toward credentials or repository access.
• Image-name or tag errors usually point toward the requested image reference.
• DNS, timeout, refused-connection, and certificate errors usually point toward connectivity or the local client path.
• An HTTP 5xx response can be transient, but it should be compared with the official status page and the scope of the failure.

Troubleshooting Docker Hub problems

1. Check for a service incident

Open the official Docker status page and look for an active incident or degraded component. If an incident is listed, save the command output and error text, then retry after recovery is reported rather than changing several local settings at once.

If no incident is listed, continue with the checks below. A normal status report does not rule out an isolated account, repository, browser, Docker client, or network problem.

2. Compare website access with Docker client access

• If hub.docker.com does not load, try another browser or network. This can help distinguish a browser, DNS, VPN, firewall, or connection problem from broader reachability trouble.
• If the website loads but docker pull or authentication fails, inspect the Docker client path, credentials, repository permissions, image name, tag, proxy, and certificate configuration.
• If only one repository or tag fails, verify the image reference and whether the account is allowed to access it. A single failed image request does not establish that Docker Hub is unavailable.

3. Check browser and account causes

For a website login or session problem, try a private browsing window, temporarily disable extensions that modify requests, and sign in again. If the same account-specific error follows you across browsers and networks, use that message to investigate credentials or permissions instead of repeatedly clearing browser data.

4. Check DNS, network, proxy, and firewall causes

A DNS failure, connection timeout, or refused connection can block Docker Hub while the service is operating normally. Test name resolution and connectivity from the affected machine, and check whether a corporate proxy, VPN, firewall, or TLS-inspecting gateway is blocking Docker traffic. Compare with another network when possible.

For related symptoms, see [DNS resolution failures](/guides/dns-probe-finished-bad-config), [connection timeouts](/guides/err-connection-timed-out), and [refused connections](/guides/err-connection-refused).

5. Interpret Docker client errors

Record the complete error before repeating the operation. Authentication or permission messages suggest an account or repository issue; name or tag messages suggest the image reference; network and certificate messages suggest connectivity or local Docker configuration.

For HTTP 500, 502, 503, or 504 responses, compare the error with the official status page and consult the relevant guidance:

• [HTTP 500 Internal Server Error](/guides/http-500-internal-server-error)
• [HTTP 502 Bad Gateway](/guides/http-502-bad-gateway)
• [HTTP 503 Service Unavailable](/guides/http-503-service-unavailable)
• [HTTP 504 Gateway Timeout](/guides/http-504-gateway-timeout)