Dev tools / Container registry / Docker Hub

Docker Hub

OPERATIONAL

Since Aug 2026 · 25 incidents · www.dockerstatus.com · checked 2m ago

CompareStatus page
GradeA+Last 59 days
A+PRODA+SHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a widespread Sev 1 the provider posted itself. A best case.
100.000%Grade A+
IncidentsEverything posted on the status page except scheduled maintenance.
40 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
11m
LongestLongest single incident, start to resolved.
1h 26m
Since lastTime since the last counted incident was resolved.
37h 18m

By area

A+Production
0INCIDENTS
0mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 1Aug 24, 2026 · 0mIncrease in service errors for Testcontainers Cloud and Offload
SEV 1Aug 24, 2026 · 0mCreating new DHI mirrored repositories is currently unavailable
Worse. 2 in the last 6 months, 0 in the 6 before.
A+Shipping
4INCIDENTS
1h 42mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Oct 21, 2026 · 1h 26mDegraded performance and intermittent availability on Docker Hub
SEV 3Oct 9, 2026 · 11mHub Registry Authenticated Actions Failing
SEV 2Aug 24, 2026 · 0mDegraded Hub performance
Worse. 17 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Worse. 25 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down0
Sev 3 · Can't shipCan't deploy, build or manage it4
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
3.3Last 12 months
Update gapMedian time between status page updates during an incident.
35mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 4Sev 1–2

Incident history

Oct 21, 20261h 26mSEV 3
Degraded performance and intermittent availability on Docker HubDocker Hub web interface and authentication had slow responses and intermittent errors from 14:14 to 15:39 UTC on October 21. Some users had login failures or delays, and API requests were also affected. The provider said a root cause was identified and fixed, but did not describe it publicly.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Web interface and login had slow responses and intermittent errors for about 85 minutes; API requests were also affected, scope not stated.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 14:14 UTC · investigating
    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
  2. 14:53 UTC · monitoring
    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.
  3. 15:39 UTC · resolved
    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.
Source
Oct 9, 202611mSEV 3
Hub Registry Authenticated Actions FailingSev 3 from the incident title (no components listed)
3 updates
  1. 21:45 UTC · identified
    All registry traffic for authenticated requests are sending back a 500.
  2. 21:52 UTC · monitoring
    We've applied a fix and are monitoring for further disruption.
  3. 21:55 UTC · resolved
    All functionality is restored on Hub Registry.
Source
Sep 14, 20265mSEV 3
Issues viewing newly pushed images and tagsSev 3 from the incident title (no components listed)
2 updates
  1. 13:29 UTC · monitoring
    We have restored processing for newly pushed images and tags and are monitoring recovery. Pushed tags were stored correctly and have not been lost.
  2. 13:34 UTC · resolved
    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.
Source
Aug 24, 20260mSEV 3
Tags pushed on July 29th may not be visible in HubSev 3 from the incident title (no components listed)
7 updates
  1. 07:19 UTC · identified
    Users 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 investigating.
  2. 07:41 UTC · identified
    We are actively working on restoring access to missing tags in Hub
  3. 10:24 UTC · identified
    We are still working on backfilling the missing tags. Thank you for your patience
  4. 14:10 UTC · identified
    While we are working on restoring missing tags, until this issue is resolved, users may experience inconsistencies in newly added/deleted tags in Hub UI. All are still pullable as expected. Please do note that webhooks and other type of update notifications could be re-sent more than once during the resolution process.
  5. 15:50 UTC · monitoring
    All remediation steps have been completed successfully. The team is continuing to monitor all subsystems.
  6. 15:56 UTC · monitoring
    All remediation steps have been completed successfully. All Docker Hub functionality has returned to normal. The team is continuing to monitor all subsystems.
  7. 20:48 UTC · resolved
    Resolved
Source
Aug 24, 20260mSEV 3
hub.docker.com has degraded performanceSev 3 from the incident title (no components listed)
2 updates
  1. 16:34 UTC · monitoring
    Users may experience timeouts on the website
  2. 18:13 UTC · resolved
    Service are restored back to normal
Source
Aug 24, 20260mSEV 3
Hub may experience intermittent timeoutsSev 3 from the incident title (no components listed)
5 updates
  1. 05:34 UTC · identified
    The team has identified an issue which could cause timeouts on hub.docker.com
  2. 06:05 UTC · monitoring
    We've implemented a fix for the issues
  3. 06:36 UTC · investigating
    We've noticed we are still not fully recovered and are investigating
  4. 07:04 UTC · monitoring
    Services should be restored back to normal
  5. 08:00 UTC · resolved
    The system has been restored to normal operational levels
Source
Aug 24, 20260mSEV 4
Emails are not being delivered due to vendor outageSev 4 from the incident title (no components listed)
3 updates
  1. 19:19 UTC · investigating
    Our third party email provider is having issues. We're investigating workarounds.
  2. 19:42 UTC · monitoring
    Provider seems to have fixed the issue.
  3. 19:57 UTC · resolved
    Vendor issue resolved
Source
Aug 24, 20260mSEV 3
Users may experience increased error rate for pushSev 3 from the incident title (no components listed)
2 updates
  1. 15:00 UTC · monitoring
    Users may have experienced increased error rates for push since around 3:30 PM UTC. The issue has been identified and fixed. We are monitoring
  2. 15:49 UTC · resolved
    Error rates are back to normal
Source
Aug 24, 20260mSEV 3
Customers are experiencing Image push webhooks not firing as expectedSev 3 from the incident title (no components listed)
5 updates
  1. 12:15 UTC · investigating
    We are aware of the issue and investigating
  2. 12:24 UTC · identified
    We identified the cause of the issue and are working on a fix.
  3. 12:49 UTC · monitoring
    The issue is now resolved, we are monitoring
  4. 12:59 UTC · monitoring
    Operational - still monitoring
  5. 13:43 UTC · resolved
    The issue is now resolved
Source
Aug 24, 20260mSEV 2
Degraded Hub performanceSev 2 from the incident title (no components listed)
6 updates
  1. 08:48 UTC · investigating
    We are investigating latency issues for Hub
  2. 09:50 UTC · monitoring
    Docker Hub performances are back to normal, we are monitoring.
  3. 11:48 UTC · investigating
    Some Docker Hub pages cannot be loaded. We are investigating what is causing the disruption.
  4. 13:57 UTC · investigating
    Service is improving, but Docker Hub is still experiencing latency issues. We are continuing to investigate.
  5. 12:20 UTC · monitoring
    Docker Hub performances are back to normal, we are monitoring.
  6. 14:32 UTC · resolved
    Docker Hub performances are back to normal.
Source
Aug 24, 20260mSEV 3
Automated Builds and BitbucketSev 3 from the incident title (no components listed)
3 updates
  1. 15:31 UTC · investigating
    An 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
  2. 16:42 UTC · monitoring
    The fix has deployed. We are now monitoring the situation
  3. 16:43 UTC · resolved
    Issue appears to be resolved
Source
Aug 24, 20260mSEV 3
Degraded Hub performanceSev 3 from the incident title (no components listed)
2 updates
  1. 18:02 UTC · identified
    We've identified an increase in error rates for Docker Hub as a result of maintenance. We're working to mitigate the issues.
  2. 19:18 UTC · resolved
    Internal maintenance has completed, system has recovered.
Source
Aug 24, 20260mSEV 3
Transient issue for accessing newly created repositories from Hub UISev 3 from the incident title (no components listed)
2 updates
  1. 10:11 UTC · monitoring
    Users may have encountered issues for accessing newly created repositories in Docker Hub between 8-9AM UTC today. Pulling and pushing was working as expected. The system is currently stable, we are monitoring.
  2. 11:39 UTC · resolved
    The system remains stable. We will continue monitoring and investigate the service degradation happened between 8AM and 10AM CET.
Source
Aug 24, 20260mSEV 4
Authentication errors and delays when signing into Docker DesktopSev 4 from the incident title (no components listed)
3 updates
  1. 18:00 UTC · investigating
    We are investigating reports of authentication failures and latency when logging into Docker Desktop.
  2. 18:48 UTC · monitoring
    Our authentication provider has identified an issue, implemented mitigation actions, and are now monitoring. Sign-in functionality has returned to normal levels. Users may experience issues signing out or restarting Desktop if running docker-mcp and may need to force close the process. We are continuing to monitor the situation closely as the provider completes their recovery.
  3. 19:19 UTC · resolved
    Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.
Source
Aug 24, 20260mSEV 4
Investigating issues signing into Docker DesktopSev 4 from the incident title (no components listed)
3 updates
  1. 19:36 UTC · investigating
    We are investigating an issue some customers reported regarding Docker Desktop authentication. Affected users may experience an immediate session termination/sign-out following a successful login attempt.
  2. 21:17 UTC · monitoring
    Authentication services remain stable. We have identified client-specific network configuration issues unrelated to Docker services. We are continuing to work directly with the affected customers toward a resolution.
  3. 00:31 UTC · resolved
    Authentication services remain stable. We are continuing to work directly with the affected customers on client-specific issues unrelated to Docker services.
Source
Aug 24, 20260mSEV 4
Issue creating new organizationsSev 4 from the incident title (no components listed)
2 updates
  1. 21:48 UTC · monitoring
    Users were encountering issues while attempting to create new organizations. This has been fixed and we are monitoring the situation.
  2. 22:56 UTC · resolved
    Errors affecting organization creation have been resolved and systems remain stable.
Source
Aug 24, 20260mSEV 4
Internal auth system failures affecting logins across the platformSev 4 from the incident title (no components listed)
4 updates
  1. 16:50 UTC · investigating
    Calls requiring auth are failing across the platform
  2. 16:53 UTC · identified
    A fix is in progress and we hope things should start to recover soon
  3. 16:56 UTC · monitoring
    The fix has been successful. We're monitoring for errors.
  4. 17:09 UTC · resolved
    The incident is resolved. Authentication is working normally.
Source
Aug 24, 20260mSEV 3
Docker Hub degradationSev 3 from the incident title (no components listed)
4 updates
  1. 13:19 UTC · investigating
    Due to one of our cloud providers, we are experiencing degradation on Docker Hub, in particular on Docker Registry Push and Pull operations.
  2. 13:21 UTC · investigating
    Due to one of our cloud providers, we are experiencing degradation on Docker Hub, in particular on Docker Registry Push and Pull operations.
  3. 13:43 UTC · monitoring
    We identified the issue and all Docker Hub functionalities looks now fully operational. We keep monitoring all the Docker Hub web services.
  4. 15:29 UTC · resolved
    Our provider communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.
Source
Aug 24, 20260mSEV 2
Increased 500 errors on Hub and RegistrySev 2 from the incident title (no components listed)
3 updates
  1. 09:04 UTC · investigating
    We are observing increased error rates accessing Docker Hub and Registry as well as other web properties. We are investigating.
  2. 09:17 UTC · monitoring
    Systems are operational but we continue monitoring them.
  3. 09:58 UTC · resolved
    Incident resolved.
Source
Aug 24, 20260mSEV 1
Increase in service errors for Testcontainers Cloud and OffloadSev 1 from the incident title (no components listed)
2 updates
  1. 11:57 UTC · identified
    We are seeing a spike in control plane errors across services due to issues with Cloudflare's global network.
  2. 17:24 UTC · resolved
    Cloudflare has recovered and so have Testcontainers Cloud and Offload.
Source
Aug 24, 20260mSEV 3
Login failuresSev 3 from the incident title (no components listed)
4 updates
  1. 19:43 UTC · identified
    We are experiencing issues with our authentication provider which might be effecting Docker hub logins for certain customers.
  2. 20:18 UTC · identified
    We are continuing to work with with our authentication provider on issues which might be affecting Docker Hub logins for certain customers.
  3. 20:38 UTC · monitoring
    We are seeing signs of recovery with our authentication provider. Docker engineers are continuing to monitor,
  4. 20:42 UTC · resolved
    This issue is resolved. Thank you for your patience.
Source
Aug 24, 20260mSEV 1
Creating new DHI mirrored repositories is currently unavailableSev 1 from the incident title (no components listed)
4 updates
  1. 07:28 UTC · investigating
    We are investigating issues when creating new DHI mirrored repositories. This currently fails with an error `Failed to mirror repository. Try again` This is only affecting new repository mirrors. Existing mirrors continue to receive updates.
  2. 07:32 UTC · identified
    We have identified the underlying issues and are working on a resolution.
  3. 07:54 UTC · monitoring
    We have deployed a fix for this issue. Creating new DHI repository mirrors available again.
  4. 07:55 UTC · resolved
    We are not seeing errors creating new DHI repository mirrors. This issue has been resolved. Thanks for your patience.
Source
Aug 24, 20260mSEV 3
Logins failingSev 3 from the incident title (no components listed)
4 updates
  1. 22:34 UTC · investigating
    We are investigating an issue where logins are failing for some users.
  2. 22:37 UTC · investigating
    Logins are failing for most users. We are investigating and will have an update shortly.
  3. 22:48 UTC · identified
    A change was rolled back and we are seeing recovery in user logins. We are continuing to monitor.
  4. 02:58 UTC · resolved
    After rolling out fixes earlier, we have not seen a recurrence of the login failures. The login issues have been resolved. Thank you for your patience
Source
Aug 24, 20260mSEV 4
Intermittent issues with hub and APIsSev 4 from the incident title (no components listed)
2 updates
  1. 03:58 UTC · monitoring
    We were having some issues with our API starting at 03:02 UTC. A fix was pushed at 03:21 UTC to mitigate the issues. We are now monitoring the fix.
  2. 05:46 UTC · resolved
    This has been fully resolved.
Source
Aug 24, 20260mSEV 3
Docker Build Cloud Degraded PerformanceSev 3 from the incident title (no components listed)
2 updates
  1. 19:26 UTC · identified
    We have identified a capacity issue in Docker Build Cloud related to an underlying Cloud Service Provider. A small subset of users may see delays in obtaining a builder.
  2. 20:12 UTC · resolved
    The issue has been resolved. Docker Build Cloud availability is back to normal.
Source

Peers, 90 days

Compare
Docker HubGrade A+100.00% up4 incidentsMTTR 11mnpmGrade D100.00% up9 incidentsMTTR 2h 15mGitHubGrade F99.87% up49 incidentsMTTR 1h 18m

README badge

Docker Hub's live grade, for your README.

Docker Hub grade badge
[![docker on downagain.dev](https://downagain.dev/badge/docker.svg)](https://downagain.dev/p/docker)