Delay on starting Machine Job Tasks

Cronologia

1. 13:40 UTC Pagina di stato di CircleCI · Reported Delay on starting Machine Job Tasks
2. 13:40 UTC Pagina di stato di CircleCI · In analisi Customers may be experiencing elevated wait times for Machine Job Tasks, we are investigating the root cause and will update when we know more.
3. 13:52 UTC Pagina di stato di CircleCI · In osservazione We are seeing signs of recovery and monitoring the situation.
4. 14:06 UTC Pagina di stato di CircleCI · Risolto The incident has been resolved. Thank you for your patience
5. 17:55 UTC Pagina di stato di CircleCI · Post mortem ## **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…