Skip to main content
Docker Hub logo

Is Docker Hub Down?

No — Docker Hub is up
Docker Hub's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 293 ms

Right now

The verdict is the worse of these two. How we decide

Docker Hub's status page

dockerstatus.com · read · checked every 3 minutes

Operational
Docker Hub's components, as its status page reports them
ComponentStatus
Docker AuthenticationUnder Maintenance
Docker Hub RegistryOperational
Docker Hub Web ServicesOperational
Docker Package RepositoriesOperational
Docker Hardened ImagesOperational
Docker Hub Automated BuildsOperational
Docker OffloadOperational
Docker ScoutOperational
Docker Testcontainers CloudOperational
Docker Build CloudOperational
Docker AI GovernanceOperational
Gordon AI AgentOperational
9 more, all operational · show all 21
All of Docker Hub's components
ComponentStatus
Docker AuthenticationUnder Maintenance
Docker Hub RegistryOperational
Docker Hub Web ServicesOperational
Docker Package RepositoriesOperational
Docker Hardened ImagesOperational
Docker Hub Automated BuildsOperational
Docker OffloadOperational
Docker ScoutOperational
Docker Testcontainers CloudOperational
Docker Build CloudOperational
Docker AI GovernanceOperational
Gordon AI AgentOperational
MCP GatewayOperational
Docker Model RunnerOperational
Docker SandboxesOperational
Docker.com WebsiteOperational
Docker SupportOperational
Docker BillingOperational
Docker Community ForumOperational
Docker DocumentationOperational
Docker Agentic PlatformOperational
Open their status page

FlareWarden checks

hub.docker.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
293 ms
Checked

By region

  • Amsterdam reachable, 243 ms
  • Chicago reachable, 144 ms
  • Paris reachable, 242 ms
  • San Jose reachable, 231 ms
  • Singapore reachable, 685 ms
  • Stockholm reachable, 214 ms
  • Sydney reachable, 476 ms
  • Toronto reachable, 109 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam82 ms3 ms18 ms228 ms
Chicago71 ms1 ms7 ms133 ms
Paris63 ms2 ms25 ms225 ms
San Jose103 ms3 ms12 ms215 ms
Singapore391 ms2 ms9 ms677 ms
Stockholm52 ms1 ms9 ms204 ms
Sydney203 ms1 ms11 ms467 ms
Toronto32 ms1 ms10 ms100 ms
We check that hub.docker.com loads, not every feature behind it. Test it yourself

History

Incidents Docker Hub reported

Since Oct 22, 15 days · from dockerstatus.com

Incidents
1
Major or critical
0
Median to resolve
1h 25m

  1. Degraded performance and intermittent availability on Docker Hub

    minor ·

    lasted 1h 25m

Docker Hub website availability

Measured by FlareWarden · hub.docker.com

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

Last 30 days

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

Measured by FlareWarden's own checks of hub.docker.com from multiple regions every 6 hours. Docker Hub's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Docker Hub itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Docker Hub goes down

We check Docker Hub every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required