CircleCI incident
Delay on starting Machine Job Tasks
Resolved after 26 min.
- Started
- Ended
- Worst state
- Degraded
- On CircleCI’s status page
- Source
- Components
- Machine Jobs
Timeline
- CircleCI status page · Reported Delay on starting Machine Job Tasks
- CircleCI status page · Investigating Customers may be experiencing elevated wait times for Machine Job Tasks, we are investigating the root cause and will update when we know more.
- CircleCI status page · Monitoring We are seeing signs of recovery and monitoring the situation.
- CircleCI status page · Resolved The incident has been resolved. Thank you for your patience
- CircleCI status page · Postmortem ## **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…
Cite this incident
Site Qwality, “Delay on starting Machine Job Tasks,” Oct 7, 2026, https://siteqwality.com/is-circleci-down/incidents/circleci-202610071340/
Free to quote with a link to this page.