Docker Hub Outage History
11 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Docker Hub Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 17, 2026 | Issues building DHI customizationsDue to a 3rd party vendor's outage, we're having issues building DHI customizations. We'll keep monitoring the situation. | 6h 12m | Resolved |
| Aug 4, 2026 | Automated builds and BitbucketAutomated builds are not triggered from a Git push to a Bitbucket repository. We are investigating the root cause. Git pushes on GitHub repositories are not impacted. | 1h 54m | Resolved |
| Jul 30, 2026 | Tags pushed on July 29th may not be visible in HubUsers may experience missing tags on Hub, for tags pushed on July 29th. Begin time: 2026-07-29 14:27:39 UTC end time: 2026-07-29 18:21:51 UTC They are successfully pullable, but not listed on Hub. We are… | 37h 16m | Resolved |
| Jul 24, 2026 | hub.docker.com has degraded performance Users may experience timeouts on the website | 1h 32m | Resolved |
| Jul 13, 2026 | Emails are not being delivered due to vendor outageOur third party email provider is having issues. We're investigating workarounds. | 30 min | Resolved |
| Jun 4, 2026 | Customers are experiencing Image push webhooks not firing as expectedWe are aware of the issue and investigating | 1h 24m | Resolved |
| Jun 3, 2026 | Users may experience increased error rate for pushUsers may have experienced increased error rates for push since around 3:30 PM UTC. The issue has been identified and fixed. We are monitoring | 42 min | Resolved |
| May 28, 2026 | Scheduled Database MaintenanceScheduled Maintenance | 2h 0m | Scheduled |
| Apr 20, 2026 | Docker Hub SSO authentication degradationUsers can't authenticate using the "Continue with SSO" button on the authentication page. However, authenticating with the email still works | 8 min | Resolved |
| Apr 20, 2026 | Degraded Hub performanceWe are investigating latency issues for Hub | 29h 34m | Resolved |
| Apr 15, 2026 | Automated Builds and BitbucketAn issue has been discovered in the communication between Docker Hub Automated Builds and Bitbucket. This may cause issues with: - Linking to Bitbucket accounts from Docker Hub - Configuring Builds with Bitbucket | 1h 9m | Resolved |
How to Read This Docker Hub Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Docker Hub acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Docker Hub outage in this window ran 1d 13h, against a mean recovery of 7h 29m. If you depend on Docker Hub in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.