Circle CI incident
Delays in starting jobs using the gen3 resource class
Circle CI experienced a minor incident on July 22, 2026 affecting Machine Jobs, lasting 6h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 22, 2026, 07:57 PM UTC
We are investigating delays in starting jobs using the gen3 resource class.
- investigating Jul 22, 2026, 08:43 PM UTC
We are continuing to investigate elevated wait times affecting customers using gen3 machine executors. Affected jobs may take longer than usual to start. We will provide another update as soon as we have more information to share.
- investigating Jul 22, 2026, 11:17 PM UTC
We are continuing to investigate elevated wait times affecting customers using gen3 machine executors. Affected jobs may take longer than usual to start. We will provide another update as soon as we have more information to share.
- investigating Jul 23, 2026, 12:31 AM UTC
We have identified the issue and are working with our provider to resolve the availability of gen 3 resources. Gen 1 and Gen 2 are both fully operational.
- resolved Jul 23, 2026, 02:05 AM UTC
Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them. Unfortunately, workflows that we were unable to provision compute capacity for during this period were cancelled. Affected customers should change their resource class from gen3 to gen2 and rerun those workflows. We thank you for your patience while our team worked to resolve this.