All services / Developer tools

Docker Hub

Current assessment
Observed reachable
Confidence
Low confidence
Scope
Observed endpoint
Last verified
Oct 25, 01:34 AM UTC
Sources
Korantix

Official incident history

  1. Degraded performance and intermittent availability on Docker Hub

    Started: · Duration: 86 min
    Provider updates (3)
    1. 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 authent…”
    2. 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. 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.”
    Resolved

  2. Hub Registry Authenticated Actions Failing

    Started: · Duration: 11 min
    Provider updates (3)
    1. Identified “All registry traffic for authenticated requests are sending back a 500.”
    2. Monitoring “We've applied a fix and are monitoring for further disruption.”
    3. Resolved “All functionality is restored on Hub Registry.”
    Resolved

  3. Issues viewing newly pushed images and tags

    Started: · Duration: 5 min
    Provider updates (2)
    1. 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. 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.”
    Resolved

  4. Tags pushed on July 29th may not be visible in Hub

    Started: · Duration: 2250 min
    Provider updates (3)
    1. 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. Monitoring “All remediation steps have been completed successfully. The team is continuing to monitor all subsystems.”
    3. Resolved “Resolved”
    Resolved

  5. hub.docker.com has degraded performance

    Started: · Duration: 100 min
    Provider updates (2)
    1. Monitoring “Users may experience timeouts on the website”
    2. Resolved “Service are restored back to normal”
    Resolved

  6. Hub may experience intermittent timeouts

    Started: · Duration: 146 min
    Provider updates (5)
    1. Identified “The team has identified an issue which could cause timeouts on hub.docker.com”
    2. Monitoring “We've implemented a fix for the issues”
    3. Investigating “We've noticed we are still not fully recovered and are investigating”
    4. Monitoring “Services should be restored back to normal”
    5. Resolved “The system has been restored to normal operational levels”
    Resolved

  7. Emails are not being delivered due to vendor outage

    Started: · Duration: 38 min
    Provider updates (3)
    1. Investigating “Our third party email provider is having issues. We're investigating workarounds.”
    2. Monitoring “Provider seems to have fixed the issue.”
    3. Resolved “Vendor issue resolved”
    Resolved

  8. Customers are experiencing Image push webhooks not firing as expected

    Started: · Duration: 88 min
    Provider updates (4)
    1. Investigating “We are aware of the issue and investigating”
    2. Identified “We identified the cause of the issue and are working on a fix.”
    3. Monitoring “The issue is now resolved, we are monitoring”
    4. Resolved “The issue is now resolved”
    Resolved

  9. Users may experience increased error rate for push

    Started: · Duration: 50 min
    Provider updates (2)
    1. 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. Resolved “Error rates are back to normal”
    Resolved

  10. Degraded Hub performance

    Started: · Duration: 1784 min
    Provider updates (5)
    1. Investigating “We are investigating latency issues for Hub”
    2. Monitoring “Docker Hub performances are back to normal, we are monitoring.”
    3. Investigating “Some Docker Hub pages cannot be loaded. We are investigating what is causing the disruption.”
    4. Monitoring “Docker Hub performances are back to normal, we are monitoring.”
    5. Resolved “Docker Hub performances are back to normal.”
    Resolved

  11. Automated Builds and Bitbucket

    Started: · Duration: 73 min
    Provider updates (3)
    1. 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. Monitoring “The fix has deployed. We are now monitoring the situation”
    3. Resolved “Issue appears to be resolved”
    Resolved

  12. Degraded Hub performance

    Started: · Duration: 77 min
    Provider updates (2)
    1. 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. Resolved “Internal maintenance has completed, system has recovered.”
    Resolved

  13. Transient issue for accessing newly created repositories from Hub UI

    Started: · Duration: 89 min
    Provider updates (2)
    1. 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. Resolved “The system remains stable. We will continue monitoring and investigate the service degradation happened between 8AM and 10AM CET.”
    Resolved

  14. Authentication errors and delays when signing into Docker Desktop

    Started: · Duration: 79 min
    Provider updates (3)
    1. Investigating “We are investigating reports of authentication failures and latency when logging into Docker Desktop.”
    2. 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. Resolved “Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.”
    Resolved

  15. Investigating issues signing into Docker Desktop

    Started: · Duration: 295 min
    Provider updates (3)
    1. 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. 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. Resolved “Authentication services remain stable. We are continuing to work directly with the affected customers on client-specific issues unrelated to Docker services.”
    Resolved

  16. Issue creating new organizations

    Started: · Duration: 68 min
    Provider updates (2)
    1. Monitoring “Users were encountering issues while attempting to create new organizations. This has been fixed and we are monitoring the situation.”
    2. Resolved “Errors affecting organization creation have been resolved and systems remain stable.”
    Resolved

  17. Internal auth system failures affecting logins across the platform

    Started: · Duration: 19 min
    Provider updates (4)
    1. Investigating “Calls requiring auth are failing across the platform”
    2. Identified “A fix is in progress and we hope things should start to recover soon”
    3. Monitoring “The fix has been successful. We're monitoring for errors.”
    4. Resolved “The incident is resolved. Authentication is working normally.”
    Resolved

  18. Increased 500 errors on Hub and Registry

    Started: · Duration: 53 min
    Provider updates (3)
    1. Investigating “We are observing increased error rates accessing Docker Hub and Registry as well as other web properties. We are investigating.”
    2. Monitoring “Systems are operational but we continue monitoring them.”
    3. Resolved “Incident resolved.”
    Resolved

  19. Docker Hub degradation

    Started: · Duration: 129 min
    Provider updates (3)
    1. 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. Monitoring “We identified the issue and all Docker Hub functionalities looks now fully operational. We keep monitoring all the Docker Hub web services.”
    3. Resolved “Our provider communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.”
    Resolved

  20. Increase in service errors for Testcontainers Cloud and Offload

    Started: · Duration: 326 min
    Provider updates (2)
    1. Identified “We are seeing a spike in control plane errors across services due to issues with Cloudflare's global network.”
    2. Resolved “Cloudflare has recovered and so have Testcontainers Cloud and Offload.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Korantix
HTTP 200 · 985 ms · Oct 25, 01:34 AM UTC

Why this assessment

  • Korantix reached the endpoint (HTTP 200, 985 ms). This only shows that the endpoint answered.
  • 985 ms is within this service's usual range (median 547 ms, p95 840 ms over 655 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Korantix3 min agoYes — recent

Technical details

Affected components (provider)

This provider has no machine-readable status source; components are not available.

Official status page ↗