Skip to content

Outage tracker / Docker Hub

Is Docker Hub down?

I'm having a problem

Vendor reports no incidentWhat Docker Hub reports

Docker Hub reports no incident on its status page.

As of the last successful poll, 2026-10-19 20:50 UTC.

Docker Hub's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Docker Hub pass from all 10 regions we check.

As of Oct 19, 2026, 8:56 PM UTC, RealUptime's checks of Docker Hub passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 8:56 PM UTC
US-East1004 msChecks passing
US-West1002 msChecks passing
Europe975 msChecks passing
Asia-Pacific1209 msChecks passing
US-Central1083 msChecks passing
Canada1081 msChecks passing
UK1093 msChecks passing
Southeast Asia1599 msChecks passing
Australia488 msChecks passing
South America2242 msChecks passing
their status pagetheir claim, not our reading

Docker Hub reports: All systems operational (“All Systems Operational”)

from Docker Hub's own status page, checked Oct 19, 2026, 8:49 PM UTC
Docker Hub's own status page shows no incident, and our checks of Docker Hub pass right now.

Docker Hub's own component breakdown, as they publish it

  • Docker AuthenticationOperational
  • 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

These are Docker Hub's components, named and scored by Docker Hub. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Docker Hub's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Docker Hub response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 913ms2026-09-21 UTC: p95 932ms2026-09-22 UTC: p95 856ms2026-09-23 UTC: p95 960ms2026-09-24 UTC: p95 939ms2026-09-25 UTC: p95 729ms2026-09-26 UTC: p95 814ms2026-09-27 UTC: p95 794ms2026-09-28 UTC: p95 823ms2026-09-29 UTC: p95 799ms2026-09-30 UTC: p95 741ms2026-10-01 UTC: p95 744ms2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 538ms2026-10-04 UTC: p95 560ms2026-10-05 UTC: p95 604ms2026-10-06 UTC: p95 708ms2026-10-07 UTC: p95 705ms2026-10-08 UTC: p95 602ms2026-10-09 UTC: p95 575ms2026-10-10 UTC: p95 560ms2026-10-11 UTC: p95 583ms2026-10-12 UTC: p95 566ms2026-10-13 UTC: p95 629ms2026-10-14 UTC: p95 629ms2026-10-15 UTC: p95 598ms2026-10-16 UTC: p95 655ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
US-West
1.5sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 826ms2026-09-21 UTC: p95 945ms2026-09-22 UTC: p95 911ms2026-09-23 UTC: p95 763ms2026-09-24 UTC: p95 812ms2026-09-25 UTC: p95 899ms2026-09-26 UTC: p95 673ms2026-09-27 UTC: p95 689ms2026-09-28 UTC: p95 674ms2026-09-29 UTC: p95 446ms2026-09-30 UTC: p95 448ms2026-10-01 UTC: p95 492ms2026-10-02 UTC: p95 465ms2026-10-03 UTC: p95 496ms2026-10-04 UTC: p95 495ms2026-10-05 UTC: p95 572ms2026-10-06 UTC: p95 551ms2026-10-07 UTC: p95 558ms2026-10-08 UTC: p95 494ms2026-10-09 UTC: p95 514ms2026-10-10 UTC: p95 494ms2026-10-11 UTC: p95 468ms2026-10-12 UTC: p95 601ms2026-10-13 UTC: p95 624ms2026-10-14 UTC: p95 665ms2026-10-15 UTC: p95 757ms2026-10-16 UTC: p95 676ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 552ms2026-09-21 UTC: p95 596ms2026-09-22 UTC: p95 561ms2026-09-23 UTC: p95 458ms2026-09-24 UTC: p95 468ms2026-09-25 UTC: p95 509ms2026-09-26 UTC: p95 550ms2026-09-27 UTC: p95 553ms2026-09-28 UTC: p95 773ms2026-09-29 UTC: p95 943ms2026-09-30 UTC: p95 916ms2026-10-01 UTC: p95 819ms2026-10-02 UTC: p95 369ms2026-10-03 UTC: p95 389ms2026-10-04 UTC: p95 339ms2026-10-05 UTC: p95 381ms2026-10-06 UTC: p95 344ms2026-10-07 UTC: p95 489ms2026-10-08 UTC: p95 518ms2026-10-09 UTC: p95 497ms2026-10-10 UTC: p95 546ms2026-10-11 UTC: p95 529ms2026-10-12 UTC: p95 499ms2026-10-13 UTC: p95 417ms2026-10-14 UTC: p95 451ms2026-10-15 UTC: p95 406ms2026-10-16 UTC: p95 414ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
Asia-Pacific
1.9sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 938ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 951ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 930ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 848ms2026-10-01 UTC: p95 849ms2026-10-02 UTC: p95 938ms2026-10-03 UTC: p95 944ms2026-10-04 UTC: p95 930ms2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 994ms2026-10-11 UTC: p95 996ms2026-10-12 UTC: p95 987ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 990ms2026-10-16 UTC: p95 987ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
US-Central
1.5sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 658ms2026-09-21 UTC: p95 648ms2026-09-22 UTC: p95 619ms2026-09-23 UTC: p95 613ms2026-09-24 UTC: p95 625ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 950ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 651ms2026-09-30 UTC: p95 660ms2026-10-01 UTC: p95 669ms2026-10-02 UTC: p95 632ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 751ms2026-09-21 UTC: p95 865ms2026-09-22 UTC: p95 778ms2026-09-23 UTC: p95 850ms2026-09-24 UTC: p95 959ms2026-09-25 UTC: p95 862ms2026-09-26 UTC: p95 759ms2026-09-27 UTC: p95 796ms2026-09-28 UTC: p95 754ms2026-09-29 UTC: p95 657ms2026-09-30 UTC: p95 726ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 979ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s
Sep 20Oct 4Oct 19
UK
1.2sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 428ms2026-09-21 UTC: p95 595ms2026-09-22 UTC: p95 553ms2026-09-23 UTC: p95 564ms2026-09-24 UTC: p95 613ms2026-09-25 UTC: p95 452ms2026-09-26 UTC: p95 430ms2026-09-27 UTC: p95 379ms2026-09-28 UTC: p95 364ms2026-09-29 UTC: p95 381ms2026-09-30 UTC: p95 386ms2026-10-01 UTC: p95 496ms2026-10-02 UTC: p95 708ms2026-10-03 UTC: p95 727ms2026-10-04 UTC: p95 649ms2026-10-05 UTC: p95 532ms2026-10-06 UTC: p95 507ms2026-10-07 UTC: p95 546ms2026-10-08 UTC: p95 582ms2026-10-09 UTC: p95 544ms2026-10-10 UTC: p95 544ms2026-10-11 UTC: p95 497ms2026-10-12 UTC: p95 559ms2026-10-13 UTC: p95 586ms2026-10-14 UTC: p95 475ms2026-10-15 UTC: p95 517ms2026-10-16 UTC: p95 487ms2026-10-17 UTC: p95 862ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 957ms2026-09-21 UTC: p95 905ms2026-09-22 UTC: p95 988ms2026-09-23 UTC: p95 881ms2026-09-24 UTC: p95 950ms2026-09-25 UTC: p95 849ms2026-09-26 UTC: p95 771ms2026-09-27 UTC: p95 843ms2026-09-28 UTC: p95 880ms2026-09-29 UTC: p95 876ms2026-09-30 UTC: p95 709ms2026-10-01 UTC: p95 772ms2026-10-02 UTC: p95 772ms2026-10-03 UTC: p95 676ms2026-10-04 UTC: p95 702ms2026-10-05 UTC: p95 835ms2026-10-06 UTC: p95 738ms2026-10-07 UTC: p95 712ms2026-10-08 UTC: p95 759ms2026-10-09 UTC: p95 740ms2026-10-10 UTC: p95 707ms2026-10-11 UTC: p95 646ms2026-10-12 UTC: p95 693ms2026-10-13 UTC: p95 782ms2026-10-14 UTC: p95 844ms2026-10-15 UTC: p95 841ms2026-10-16 UTC: p95 864ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
South America
2.2sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 966ms2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 974ms2026-10-05 UTC: p95 973ms2026-10-06 UTC: p95 982ms2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s
Sep 20Oct 4Oct 19

Check your own site while you wait on Docker Hub

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Docker Hub. It cannot diagnose Docker Hub's own systems.

Email me when Docker Hub reports an incident on its status page, and again when it reports it resolved.

Get an email when Docker Hub reports an incident

Email me when Docker Hub reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Docker Hub's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1004msstatus code: 200checked: Oct 19, 2026, 8:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Docker Hub normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1002msstatus code: 200checked: Oct 19, 2026, 8:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Docker Hub normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 1083msstatus code: 200checked: Oct 19, 2026, 8:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Docker Hub normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1081msstatus code: 200checked: Oct 19, 2026, 8:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Docker Hub normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2242msstatus code: 200checked: Oct 19, 2026, 8:42 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Docker Hub normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 975msstatus code: 200checked: Oct 19, 2026, 8:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Docker Hub normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1093msstatus code: 200checked: Oct 19, 2026, 8:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Docker Hub normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1209msstatus code: 200checked: Oct 19, 2026, 8:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Docker Hub normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1599msstatus code: 200checked: Oct 19, 2026, 8:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Docker Hub normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 488msstatus code: 200checked: Oct 19, 2026, 8:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Docker Hub normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Docker Hub, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Docker Hub yet, which is not evidence that nothing is wrong.

Recent probe events

Hub Registry Authenticated Actions Failing, 11mdeclared on their status page2026-10-09
Issues viewing newly pushed images and tags, 5mdeclared on their status page2026-09-14
Tags pushed on July 29th may not be visible in Hub, 37h 30mdeclared on their status page2026-07-30
hub.docker.com has degraded performance, 1h 40mdeclared on their status page2026-07-24
Hub may experience intermittent timeouts, 2h 26mdeclared on their status page2026-07-22
Emails are not being delivered due to vendor outage, 38mdeclared on their status page2026-07-13
Customers are experiencing Image push webhooks not firing as expected, 1h 28mdeclared on their status page2026-06-04
Users may experience increased error rate for push, 50mdeclared on their status page2026-06-03

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Docker Hub since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Docker Hub covering any window you pick, with our check readings and Docker Hub's own claim at the time, side by side.

Full check history for Docker Hub: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Docker Hub uptime by RealUptime's checksLive, from this page's own readings.
[![Docker Hub uptime by RealUptime's checks](https://realuptime.io/outages/docker-hub/badge.svg?days=30)](https://realuptime.io/outages/docker-hub)
<a href="https://realuptime.io/outages/docker-hub"><img src="https://realuptime.io/outages/docker-hub/badge.svg?days=30" alt="Docker Hub uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Docker Hub down?", https://realuptime.io/outages/docker-hub. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://hub.docker.com/v2/repositories/library/nginx
secondary
https://www.dockerstatus.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: hub.docker.com

RealUptime is not affiliated with Docker Hub; the name identifies what we checked, and nothing here speaks for Docker Hub's own team. We send a single web request to Docker Hub from 10 regions on our own schedule and time the response. We do not see inside Docker Hub's systems, do not use an account or real transaction, and are not the same signal Docker Hub's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Docker Hub is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.