Docker

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-21 14:14 UTC

   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....

2. monitoring 2026-10-21 14:53 UTC

   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...

3. resolved 2026-10-21 15:39 UTC

   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.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-09 21:45 UTC

   All registry traffic for authenticated requests are sending back a 500.

2. monitoring 2026-10-09 21:52 UTC

   We've applied a fix and are monitoring for further disruption.

3. resolved 2026-10-09 21:55 UTC

   All functionality is restored on Hub Registry.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-14 13:29 UTC

   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. resolved 2026-09-14 13:34 UTC

   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.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-30 07:19 UTC

   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. identified 2026-07-30 07:41 UTC

   We are actively working on restoring access to missing tags in Hub

3. identified 2026-07-31 10:24 UTC

   We are still working on backfilling the missing tags. Thank you for your patience

4. identified 2026-07-31 14:10 UTC

   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...

5. monitoring 2026-07-31 15:50 UTC

   All remediation steps have been completed successfully. The team is continuing to monitor all subsystems.

6. monitoring 2026-07-31 15:56 UTC

   All remediation steps have been completed successfully. All Docker Hub functionality has returned to normal. The team is continuing to monitor all subsystems.

7. resolved 2026-07-31 20:48 UTC

   Resolved

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-24 16:34 UTC

   Users may experience timeouts on the website

2. resolved 2026-07-24 18:13 UTC

   Service are restored back to normal

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-22 05:34 UTC

   The team has identified an issue which could cause timeouts on hub.docker.com

2. monitoring 2026-07-22 06:05 UTC

   We've implemented a fix for the issues

3. investigating 2026-07-22 06:36 UTC

   We've noticed we are still not fully recovered and are investigating

4. monitoring 2026-07-22 07:04 UTC

   Services should be restored back to normal

5. resolved 2026-07-22 08:00 UTC

   The system has been restored to normal operational levels

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-13 19:19 UTC

   Our third party email provider is having issues. We're investigating workarounds.

2. monitoring 2026-07-13 19:42 UTC

   Provider seems to have fixed the issue.

3. resolved 2026-07-13 19:57 UTC

   Vendor issue resolved

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 12:15 UTC

   We are aware of the issue and investigating

2. identified 2026-06-04 12:24 UTC

   We identified the cause of the issue and are working on a fix.

3. monitoring 2026-06-04 12:49 UTC

   The issue is now resolved, we are monitoring

4. monitoring 2026-06-04 12:59 UTC

   Operational - still monitoring

5. resolved 2026-06-04 13:43 UTC

   The issue is now resolved

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-03 15:00 UTC

   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. resolved 2026-06-03 15:49 UTC

   Error rates are back to normal

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 08:48 UTC

   We are investigating latency issues for Hub

2. monitoring 2026-04-20 09:50 UTC

   Docker Hub performances are back to normal, we are monitoring.

3. investigating 2026-04-20 11:48 UTC

   Some Docker Hub pages cannot be loaded. We are investigating what is causing the disruption.

4. investigating 2026-04-20 13:57 UTC

   Service is improving, but Docker Hub is still experiencing latency issues. We are continuing to investigate.

5. monitoring 2026-04-21 12:20 UTC

   Docker Hub performances are back to normal, we are monitoring.

6. resolved 2026-04-21 14:32 UTC

   Docker Hub performances are back to normal.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-15 15:31 UTC

   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. monitoring 2026-04-15 16:42 UTC

   The fix has deployed. We are now monitoring the situation

3. resolved 2026-04-15 16:43 UTC

   Issue appears to be resolved

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-25 18:02 UTC

   We've identified an increase in error rates for Docker Hub as a result of maintenance. We're working to mitigate the issues.

2. resolved 2026-03-25 19:18 UTC

   Internal maintenance has completed, system has recovered.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-03-07 10:11 UTC

   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. resolved 2026-03-07 11:39 UTC

   The system remains stable. We will continue monitoring and investigate the service degradation happened between 8AM and 10AM CET.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-22 18:00 UTC

   We are investigating reports of authentication failures and latency when logging into Docker Desktop.

2. monitoring 2026-02-22 18:48 UTC

   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...

3. resolved 2026-02-22 19:19 UTC

   Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-07 19:36 UTC

   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. monitoring 2026-01-07 21:17 UTC

   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. resolved 2026-01-08 00:31 UTC

   Authentication services remain stable. We are continuing to work directly with the affected customers on client-specific issues unrelated to Docker services.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-05 21:48 UTC

   Users were encountering issues while attempting to create new organizations. This has been fixed and we are monitoring the situation.

2. resolved 2026-01-05 22:56 UTC

   Errors affecting organization creation have been resolved and systems remain stable.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-17 16:50 UTC

   Calls requiring auth are failing across the platform

2. identified 2025-12-17 16:53 UTC

   A fix is in progress and we hope things should start to recover soon

3. monitoring 2025-12-17 16:56 UTC

   The fix has been successful. We're monitoring for errors.

4. resolved 2025-12-17 17:09 UTC

   The incident is resolved. Authentication is working normally.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-05 09:04 UTC

   We are observing increased error rates accessing Docker Hub and Registry as well as other web properties. We are investigating.

2. monitoring 2025-12-05 09:17 UTC

   Systems are operational but we continue monitoring them.

3. resolved 2025-12-05 09:58 UTC

   Incident resolved.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 13:19 UTC

   Due to one of our cloud providers, we are experiencing degradation on Docker Hub, in particular on Docker Registry Push and Pull operations.

2. investigating 2025-11-18 13:21 UTC

   Due to one of our cloud providers, we are experiencing degradation on Docker Hub, in particular on Docker Registry Push and Pull operations.

3. monitoring 2025-11-18 13:43 UTC

   We identified the issue and all Docker Hub functionalities looks now fully operational. We keep monitoring all the Docker Hub web services.

4. resolved 2025-11-18 15:29 UTC

   Our provider communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 11:57 UTC

   We are seeing a spike in control plane errors across services due to issues with Cloudflare's global network.

2. resolved 2025-11-18 17:24 UTC

   Cloudflare has recovered and so have Testcontainers Cloud and Offload.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-16 19:43 UTC

   We are experiencing issues with our authentication provider which might be effecting Docker hub logins for certain customers.

2. identified 2025-11-16 20:18 UTC

   We are continuing to work with with our authentication provider on issues which might be affecting Docker Hub logins for certain customers.

3. monitoring 2025-11-16 20:38 UTC

   We are seeing signs of recovery with our authentication provider. Docker engineers are continuing to monitor,

4. resolved 2025-11-16 20:42 UTC

   This issue is resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-12 22:34 UTC

   We are investigating an issue where logins are failing for some users.

2. investigating 2025-11-12 22:37 UTC

   Logins are failing for most users. We are investigating and will have an update shortly.

3. identified 2025-11-12 22:48 UTC

   A change was rolled back and we are seeing recovery in user logins. We are continuing to monitor.

4. resolved 2025-11-13 02:58 UTC

   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

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-04 07:28 UTC

   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. identified 2025-11-04 07:32 UTC

   We have identified the underlying issues and are working on a resolution.

3. monitoring 2025-11-04 07:54 UTC

   We have deployed a fix for this issue. Creating new DHI repository mirrors available again.

4. resolved 2025-11-04 07:55 UTC

   We are not seeing errors creating new DHI repository mirrors. This issue has been resolved. Thanks for your patience.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-11-04 03:58 UTC

   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. resolved 2025-11-04 05:46 UTC

   This has been fully resolved.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-28 19:26 UTC

   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. resolved 2025-10-28 20:12 UTC

   The issue has been resolved. Docker Build Cloud availability is back to normal.

Excerpts are shortened. Read the full incident on Docker's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-21 08:22 UTC

   Due to yesterdays AWS outage we are still seeing disruption on the Docker Hub Automated Builds. We are investigating solutions at this time

2. monitoring 2025-10-21 09:17 UTC

   We are currently clearing up the backlog of builds that broke during the AWS incident and aim to be back online by 10:00 UTC

3. resolved 2025-10-21 09:42 UTC

   Incident has been resolved. Users should now be able to retry their builds

Excerpts are shortened. Read the full incident on Docker's status page.