Docker Outage History

During the incident, creating new DHI mirrored repositories was unavailable, causing a partial disruption for teams relying on Docker mirroring. The outage lasted approximately 20 minutes, from 7:35 AM UTC to 7:55 AM UTC, and the Docker Hardened Images component briefly transitioned to a degraded state during the incident.

The Docker status page documented two updates during the event. The first indicated that underlying issues had been identified and were being worked on, and the second confirmed that the issue was resolved and the service had returned to normal operations.

The Docker Build Cloud component experienced degraded performance beginning at Oct 28, 2025 5:30 PM UTC and resolving by Oct 28, 2025 7:30 PM UTC. Builds and related workflows relying on Docker Build Cloud may have encountered slower build times or intermittent failures during this window. The issue was isolated to the Docker Build Cloud component, with other Docker services unaffected.

Status communications on the Docker status page showed a transition from normal operation to degraded at Oct 28, 2025 5:30 PM UTC and back to normal by Oct 28, 2025 7:30 PM UTC.

Docker Hub Automated Builds experienced a temporary outage linked to the broader AWS disruption, causing automated build jobs to fail and delaying image builds for about 55 minutes.

The outage affected only the Docker Hub Automated Builds component. The Docker status page shows an initial warning at Oct 21, 2025 8:25 AM UTC, a confirmed outage at Oct 21, 2025 8:50 AM UTC, and a full recovery at Oct 21, 2025 9:45 AM UTC. The incident prompted three updates from Docker during the event, and the service returned to normal after Oct 21, 2025 9:45 AM UTC.

An extended outage affected Docker Hub, Docker Registry, Build Cloud and related services, causing image pulls and pushes to fail, logins to time out, and builds to stall for users across the globe. The problem began at 7:20 AM UTC and persisted for about 17 hours, with full restoration achieved by 12:40 AM UTC. Docker issued multiple status updates during the incident as engineers diagnosed an upstream service provider issue and worked toward remediation across components including Docker Hub, Registry, Automated Builds, Security Scanning, Authentication, and Docker Docs. StatusGator detected an Early Warning Signal at Oct 20, 2025 7:14 AM UTC, about 6 minutes before Docker's official acknowledgment, indicating activity ahead of the provider update. A high volume of user reports documented the widespread disruption, with many users unable to pull or push images, authenticate, or complete builds from multiple regions.

Docker Hardened Images experienced a brief degradation due to a cloud provider issue that caused backlogs in the DHI customization pipelines. The impact was limited to the Docker Hardened Images component and its build pipelines. The incident began at 3:20 PM UTC and was resolved by 4:35 PM UTC, lasting about 1 hour and 15 minutes. The provider posted two status updates during the incident describing the backlog and remediation efforts, and the component returned to normal once the backlog was cleared.

An outage affected Docker Docs, the documentation site for Docker. Users encountered access-denied errors when loading documentation, temporarily preventing access to guides and API references. The incident began at 5:25 PM UTC and was resolved by 5:55 PM UTC, lasting about 30 minutes. The issue was isolated to the Docker Docs component. The Docker status page posted 2 updates during the incident.

A brief degradation affected Docker Build Cloud, impacting build-related tasks for some users. User reports began around 12:45 AM UTC, with the Docker status page indicating a degraded state at 1:50 AM UTC. The issue was resolved by 2:50 AM UTC, and the outage lasted about 1 hour. The status page provided updates during the incident, noting the degraded performance of Docker Build Cloud as engineers worked to restore full service.

An authentication outage affected Docker Hub and related services, preventing sign-ins and image pulls. The incident impacted 7 components including Docker Hub Registry, Docker Authentication, Docker Scout, Docker Build Cloud, Docker Cloud, Docker Hardened Images, and Docker Hub Web Services. Users reported login failures and 401 Unauthorized errors when pulling images, with effects felt globally as developers could not download or verify images. StatusGator detected the issue at Sep 24, 2025 11:01 PM UTC, about 9 minutes before the first official acknowledgment at Sep 24, 2025 11:10 PM UTC. The Docker status page issued 3 updates during the incident, with the issue listed as an elevated error rate in authentication and registry services. The outage began on Sep 24, 2025 11:10 PM UTC and was resolved by Sep 25, 2025 1:30 AM UTC. The outage lasted roughly 2 hours and 20 minutes and generated a high volume of global user reports.

An outage affecting Docker Hub authentication and registry access caused widespread image pull failures and token fetch errors. Users reported 500 errors when pulling images, registry failures, and OAuth token fetch problems, impacting workflows that rely on Docker Hub for base images and builds. The incident appeared global, with reports from multiple regions indicating broad impact. The outage lasted roughly 22 minutes, beginning around 7:00 PM UTC and ending around 7:22 PM UTC.

Status communications from Docker were not observed in the official status page during the incident. StatusGator detected an Early Warning Signal starting at Sep 15, 2025 7:10 PM UTC and ending at 7:22 PM UTC as user reports persisted. The issue appears to have been global, based on the geographic distribution of symptoms.

Docker experienced a brief degraded login experience due to an issue in the Docker Authentication flow. Users attempting to sign in with a username or email could be stuck because they were not prompted for a password. The problem affected the authentication component and caused a short interruption in the login process for some users. The incident had a global reach based on typical usage patterns, with no specific regional concentration reported.