CircleCI favicon

CircleCI outage on 2026-10-21

circleci.com
October 2026 21 Minor incident

CircleCI's Docker Jobs component ran slow for 1h 31m on 21 October, with gen2 Docker jobs on 2xlarge seeing wait times up to 20 minutes. The delay was on CircleCI's side, caused by capacity issues on their infrastructure.

Started

19:31 UTC

Duration

Lasted 1h 31m

Source

IsDown

Next time

CircleCI is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Docker Jobs

What happened?

CircleCI logged this incident at 19:31 UTC under the title "Increased Docker gen2 wait times", attributing it to capacity issues affecting gen2 Docker jobs. At that point the only component marked as affected was Docker Jobs. By 20:03 CircleCI said it was adding capacity to help, but flagged that 2xlarge jobs were still seeing delays of up to 20 minutes. Twenty minutes later, at 20:22, CircleCI reported wait times for 2xlarge jobs recovering, and by 20:35 those wait times were under 60 seconds. The same 20:35 update clarified that other resource sizes were never affected, staying under 10 seconds throughout. CircleCI moved the incident to monitoring at 20:40 after seeing a full recovery, then resolved it at 20:54. The whole incident ran 1h 31m from first report to resolution, with six updates published across that window. No user reports were filed in this window, so there is no independent account of how the slowdown felt from outside CircleCI's own dashboards. The incident only affected one component, Docker Jobs, and CircleCI's own updates are the only record of what happened and how it resolved.

Learning

This incident was a queuing delay inside CircleCI's build infrastructure, not a case of CircleCI's API or website going down, so checking whether circleci.com loaded would have told you nothing. Delays like this show up as jobs sitting longer than usual, not as errors or outright failures, which makes them invisible to simple uptime checks on your own endpoints. CircleCI's own breakdown shows the fault was isolated to 2xlarge gen2 Docker jobs, while other resource sizes stayed under 10 seconds the entire time, so the impact depended heavily on which job size your pipelines used. Over the past 90 days CircleCI has logged 26 incidents with a median duration of 1 hour 42 minutes, and this one resolved faster than that median at 1h 31m, so some delay on their platform is a recurring condition rather than a one-off. Your own monitoring watches your product's endpoints, but it has no visibility into a provider's internal queue depth or capacity headroom. UptimeRobot now tracks CircleCI's own status history and update cadence alongside your checks, so when job times stretch out you can tell whether the problem is yours or theirs instead of guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.