Live / Docker / Incident
Docker: Degraded performance and intermittent availability on Docker Hub
Docker · docker.comMinor incidentResolved2026-10-21 15:39 UTC
Public — what happened
Summary
Docker reported a minor incident beginning at 14:14 UTC on 2026-10-21, in which Docker Hub was slow and sometimes returned errors. The company said some users could have trouble logging in or reaching the Docker Hub website, and it listed the web interface and authentication as affected. By 14:53 UTC Docker said it had found and fixed the root cause and that response times and availability were returning to normal, including for API requests. The incident was marked resolved at 15:39 UTC after a period of close monitoring.
Timeline
- Started — 2026-10-21 14:14 UTC
- Investigating — 2026-10-21 14:14 UTC
- Monitoring — 2026-10-21 14:53 UTC
- Resolved — 2026-10-21 15:39 UTC · 1h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Docker against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Docker: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Docker report →
More from Docker
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.