Docker Hub uptime
Docker Hub, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Docker Hub is up.
Up for 51 d 9 h. Last checked 2026-11-20 17:27 UTC from Singapore: 401 in 878 ms.
Last 24 hours
Up for 51 d 9 h100% passed
288 checks, median 293 ms from Copenhagen, all passed
95% under 297 ms
Response time by region
Medians over this range, on one scale up to 1,000 ms.
Last 90 days
Up for 51 d 9 h100% passed
14,788 checks, median 296 ms from Copenhagen, all passed
95% under 325 ms
Response time by region
Medians over this range, on one scale up to 1,000 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
In the last 30 days Docker Hub passed 8,845 of 8,845 checks, 100%.
No outage since checks began on 30 Sep 2026.
Availability
The share of checks that passed, and the outages that began, in each window up to now.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | 100% | 2,009 of 2,009 | 0 |
| 30 days | 100% | 8,845 of 8,845 | 0 |
| 90 days | Not enough history yet: checks began on 30 Sep 2026 | ||
A year of checks is kept; the year's figure appears here once there is a year of them.
Response time by location
Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 315 ms | 329 ms | 313 ms | 42 |
| Helsinki, Finland | 325 ms | 363 ms | 330 ms | 42 |
| Ashburn, USA | 100 ms | 197 ms | 105 ms | 502 |
| Copenhagen, Denmark | 292 ms | 299 ms | 298 ms | 419 |
| Singapore | 892 ms | 1,088 ms | 900 ms | 506 |
| Sydney, Australia | 724 ms | 920 ms | 732 ms | 505 |
Outages
None detected since checks began on 30 Sep 2026.
What is checked
Docker's public container registry, where `docker pull` looks for images that name no other registry.
StatOSS sends GET https://registry-1.docker.io/v2/ and counts the check as passed on status 401 within 10 seconds. The registry API's version check, the first request `docker pull` makes. Without a token it answers 401 and points the client at Docker's token service, as the registry specification says it should.
Layer downloads come from a CDN, and the token service and hub.docker.com are separate; a pull can fail on any of them.
Docker Hub reports its own incidents at www.dockerstatus.com. The figures here are measured from outside and can differ from it in both directions.
How it is measured
- One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
- A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
- A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
- Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
- Availability is the share of checks that passed. There are no maintenance windows: every check counts.
It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.