Who is down right now

28 down now · 290 this week

CircleCI · Developer toolsOct 7, 2026, 18:54 UTC 6 weeks ago

Increased task wait times for Docker Gen2

MinorConfig changeUpdated 43d ago
Oct 7, 18:54 UTCOct 7, 20:05 UTC
Duration
1h 11m
Impact
Minor
Root cause
Config change
CircleCI, 90 days
23 incidents
Affected
Docker Jobs
Status page

Final update

## **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 gives each job its configuration at startup ran out of memory and restarted. * **October 7, 18:49 to 20:05 UTC:** Docker Gen 2 jobs waited longer than normal because we could not acquire enough instances fr

Timeline

  1. Postmortem · Oct 8, 17:54 UTC
    ## **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 gives each job its configuration at startup ran out of memory and restarted. * **October 7, 18:49 to 20:05 UTC:** Docker Gen 2 jobs waited longer than normal because we could not acquire enough instances from our cloud provider. * **October 8, 12:48 to 16:00 UTC:** Linux machine jobs and remote Docker jobs waited up to 50 minutes to start. Our cloud provider did not have enough of the instance type we request, and a defect in the logic that picks a different instance type kept us from using alternativ
  2. Resolved · Oct 7, 20:05 UTC
    This incident has been resolved.
  3. Monitoring · Oct 7, 19:52 UTC
    We're still seeing spikes in task wait times but on average wait times are looking better for all Docker Gen2.
  4. Identified · Oct 7, 19:00 UTC
    Note: delays will be more noticeable for people running on Docker `xlarge` and above.
  5. Identified · Oct 7, 18:54 UTC
    There is an increased wait time for jobs on Docker Gen2.

More from CircleCI

Full history

Also caused by configuration change

All