Degraded performance and intermittent availability on Docker Hub
The incident has been resolved. Docker Hub is operating normally, and we have confirmed that response times and availability have returned to expected levels for all services.
The latest update from Docker.
State
Resolved
Started
11 d ago
2026-10-21 14:14 UTC
Lasted
1 h 26 min
until 2026-10-21 15:39 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
39 min 46%
Monitoring
47 min 54%
Updates
Times in UTCAs posted by Docker
The incident has been resolved. Docker Hub is operating normally, and we have confirmed that response times and availability have returned to expected levels for all services.
The root cause of the degradation was identified and fixed. All Docker Hub services are now operational and we are seeing response times and availability return to normal for the web interface and authentication, and API requests. We are continuing to monitor closely to confirm the issue is fully resolved.
We are investigating reports of slow response times and intermittent errors affecting Docker Hub. Some users may experience failures or delays when logging in, or accessing [hub.docker.com](http://hub.docker.com). Our engineering team is actively working to identify the cause. Service may be unavailable for short periods while we work on this. **Affected services:** • Web interface and authentication
Docker in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
11 min
This incident
8.2× the median
Other Docker incidents
All incidentsDocker·Hub Registry Authenticated Actions Failing
All functionality is restored on Hub Registry.
Docker·Issues viewing newly pushed images and tags
Newly pushed images and tags are now processing and appearing normally. We have resolved the issue and confirmed that pushed tags were stored correctly and were not lost.
Follow Docker
Your coding agent knows when Docker is down, and tells you when a failure is theirs, not yours. You can also get Docker incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "docker" and tell me if Docker has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=docker/feed subscribe https://outages.cc/feed.xml?providers=dockerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane