# CircleCI: Delay on starting Machine Job Tasks

- Provider: [CircleCI](https://outages.cc/circleci.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-10-07 13:40 UTC
- Resolved: 2026-10-07 14:06 UTC (lasted 26 min)
- Components: Machine Jobs
- Official update: https://stspg.io/7q8hkm5sgt8h

## Updates from CircleCI

### postmortem, 2026-10-08 17:55 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

### resolved, 2026-10-07 14:06 UTC

The incident has been resolved. Thank you for your patience

### monitoring, 2026-10-07 13:52 UTC

We are seeing signs of recovery and monitoring the situation.

### investigating, 2026-10-07 13:40 UTC

Customers may be experiencing elevated wait times for Machine Job Tasks, we are investigating the root cause and will update when we know more.