Docker Hub uptime
Docker Hub, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Docker Hub is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:36 UTC from Aarhus, Denmark: 401 in 294 ms.
Last 24 hours
Up for 6 d 3 h100% passed
288 checks, median 301 ms from Copenhagen, all passed
95% under 341 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.
Last 90 days
Up for 6 d 3 h100% passed
1,764 checks, median 290 ms from Aarhus, all passed
95% under 317 ms
Response time by region
Medians over this range, on one scale up to 1,000 ms. Europe's places are scaled to Aarhus, its fastest shared place.
In the last 24 hours Docker Hub passed 288 of 288 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 | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 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 | 309 ms | 344 ms | 313 ms | 196 |
| Ashburn, USA | 132 ms | 227 ms | 143 ms | 556 |
| Copenhagen, Denmark | 304 ms | 320 ms | 306 ms | 170 |
| Singapore | 851 ms | 1,085 ms | 880 ms | 563 |
| Sydney, Australia | 726 ms | 1,082 ms | 807 ms | 84 |
| Aarhus, Denmark | 290 ms | 333 ms | 297 ms | 195 |
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: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, 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.