Circle CI incident

Delays starting jobs on Docker (Gen 2) resource classes

Minor Resolved View vendor source →

Circle CI experienced a minor incident on July 14, 2026 affecting Docker Jobs, lasting 1h 38m. The incident has been resolved; the full update timeline is below.

Started
Jul 14, 2026, 10:54 PM UTC
Resolved
Jul 15, 2026, 12:32 AM UTC
Duration
1h 38m
Detected by Pingoru
Jul 14, 2026, 10:54 PM UTC

Affected components

Docker Jobs

Update timeline

  1. identified Jul 14, 2026, 10:54 PM UTC

    On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. Delays reached up to approximately 1 minute 48 seconds. We are continuing to experience these delays again since approximately 15:45 UTC. So far, delays have reached up to approximately 1 minute 19 seconds. We are working with our cloud provider to add capacity and will update this incident as the situation changes.

  2. resolved Jul 15, 2026, 12:32 AM UTC

    On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. The same issue recurred on July 14 between 15:45 UTC and 22:50 UTC. Delays reached up to 25 minutes on July 13 and up to 24 minutes on July 14. The medium+ and 2 X-large+ resource classes saw the longest waits. Earlier updates in this incident reported figures based on average wait times, which didn't reflect the maximum impact some customers may have experienced. Wait times have now returned to normal. We are continuing to work with our cloud provider to add capacity ahead of the next peak period. Thank you for your patience.