Operational Docker Hub status
docker.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Docker Hub looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage, Cloudflare: Degraded / minor incident
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 88 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Authentication errors and delays when signing into Docker Desktop”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services, Cloudflare report an issue. Docker Hub may depend on them (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Docker Hub's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Docker Hub may run on Amazon Web Services, Cloudflare (inferred). We don't map other services that depend on Docker Hub. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Docker Hub or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Docker Hub. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Authentication errors and delays when signing into Docker Desktop
major resolved · started · resolved
3 updates
- investigating
We are investigating reports of authentication failures and latency when logging into Docker Desktop.
- 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.
- resolved
Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.