CircleCI reported this minor-impact incident on its official status page on Nov 3, 2026, 14:14 UTC. It was resolved after 54 min.
Right now CircleCI is operational. Live CircleCI status →
## Summary From 13:55 to 15:07 UTC on November 3, customers running Linux machine jobs and Remote Docker saw increased wait times for their jobs to start, and the delays were longest from 14:16 to 14:41. Some Docker jobs also saw increased wait times. The incident was caused by our usage reaching the vCPU limit on our cloud provider account in our main cloud region. Machine and Docker jobs share this limit, and the additional Docker capacity we have run since the [October 21 incident](https://discuss.circleci.com/t/post-incident-report-oct-21-2026-increased-wait-times-for-gen-2-docker-jobs/54940) brought our usage to the limit as demand increased. Machine jobs did not move to our backup regions because our system did not treat reaching this limit the same way as a shortage of cloud instances. In response, our engineering team reconfigured machine jobs to balance across all of our regions instead of relying on backup regions, and reduced Docker capacity to make room under the limit.
Wait times have returned to normal for Machine and Remote Docker. We appreciate your patience as we worked through this.
Our team has applied a fix and we're starting to see wait times recover. We're keeping an eye on this as it continues to rollout and we'll update again shortly. We thank you again for your patience.
Some users might see increased wait times for Machine and Remote Docker jobs due to increased usage. Wait times right now are just under 7 mins. Our team is investigating and we'll post another update shortly. We appreciate your patience.
Overlapping incidents aren't necessarily related.
CircleCI reported 23 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 12m. See CircleCI's uptime and incident history