Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Docker Hub down?

Right now

No. Docker Hub is operational.

No incidents reported.

Read from www.dockerstatus.com · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/docker/status.agent.json

MCP: upstream_status {"service":"docker"}

Image pulls and pushes, Docker Build Cloud and Scout. A registry incident breaks builds and autoscaling that pull images.

What Docker Hub reports

Operational

Taken as is from Docker Hub's own status page API. Incident titles and component names below are theirs.

Open www.dockerstatus.com

UpButler's independent probe

Registry is answeringHTTP 401 · 302 ms

One request without credentials to registry-1.docker.io every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked · up since 2026-10-10 01:23 UTC

Docker Hub components

21 operational

  • 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

Docker Hub incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Docker Hub.

Started (UTC)IncidentImpactLasted
Hub Registry Authenticated Actions Failingmajor11 min

Tell your outage from Docker Hub's

Declare that your project depends on Docker Hub. When one of your monitors fails while Docker Hub has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - docker
Ask before you retry
curl -s https://upbutler.com/status/docker/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "docker",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Docker Hub down right now?
No. As of 2026-10-10 05:10 UTC, Docker Hub is operational. This page reads the status again every 2 minutes.
Where does this status come from?
From Docker Hub's own status page API at https://www.dockerstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Docker Hub's words.
What does UpButler's own Docker Hub check prove?
Every two minutes UpButler sends one request without credentials to the Docker Hub Registry (registry-1.docker.io). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Docker Hub reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Docker Hub status?
Fetch https://upbutler.com/status/docker/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"docker"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Docker Hub's?
Add "docker" to the dependencies of your UpButler workspace. When one of your monitors fails while Docker Hub has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Docker Hub. Status and incident text belong to Docker Hub and are read from their public status source; the probe result is UpButler's own measurement.