CircleCI reported this minor-impact incident on its official status page on Oct 7, 2026, 18:54 UTC. It was resolved after 1h 11m.
Right now CircleCI is operational. Live CircleCI status →
## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was caused by a configuration issue in our scheduling infrastructure, and one by memory limits on an internal service, which we raised during the incident. * **October 1, 07:57 to 10:24 UTC:** Docker Gen 2 jobs waited up to 30 minutes to start. A configuration issue prevented the Gen 2 scheduling servers from using their high-performance local disks. During a burst in traffic, the fallback disks saturated and job placement slowed. * **October 7, 13:27 to 14:06 UTC:** Machine jobs waited longer than normal because we could not acquire enough virtual machines from our cloud provider. * **October 7, 14:24 to 15:21 UTC:** Some jobs failed with an infrastructure error, and workflows were delayed. The service that give
This incident has been resolved.
We're still seeing spikes in task wait times but on average wait times are looking better for all Docker Gen2.
Note: delays will be more noticeable for people running on Docker `xlarge` and above.
There is an increased wait time for jobs on Docker Gen2.
Overlapping incidents aren't necessarily related.
CircleCI reported 28 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 38m. See CircleCI's uptime and incident history