# CircleCI: Jobs using IP ranges failing with infrastructure errors

> Docker executor jobs with the IP ranges feature enabled failed at a higher rate with infrastructure errors. CircleCI reports that the incident is resolved and lasted about 2 hours and 26 minutes. A workaround was to rerun the failed job.

- Provider: [CircleCI](https://outages.live/circleci.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-11-20 21:22 UTC
- Resolved: 2026-11-20 23:48 UTC (lasted 2 h 26 min)
- Components: Docker Jobs
- Official update: https://stspg.io/m8bpg1brfjcw

## Updates from CircleCI

### resolved, 2026-11-20 23:48 UTC

We have seen recovery for IP range jobs for gen2 docker jobs. We appreciate your patience while we worked through the incident.

### monitoring, 2026-11-20 23:12 UTC

We are continuing to monitor the rollout for recovery.

### monitoring, 2026-11-20 22:30 UTC

A fix has been fully deployed, we are now monitoring for recovery.

### identified, 2026-11-20 22:21 UTC

The fix for IP range docker jobs are rolling out across the fleet. We will monitor for recovery in infra fails.

### identified, 2026-11-20 22:00 UTC

We are continuing to rollout a fix for IP range docker jobs. Customers may continue to retry jobs that use IP ranges that experience infra fails. We will provide an update within 20 minutes on the fix.

### identified, 2026-11-20 21:24 UTC

Customers running Docker executor jobs with the IP ranges feature enabled are experiencing a higher rate of infrastructure failures. A fix is being rolled out. Customers who see an infrastructure failure on one of these jobs can rerun the failed job. We will provide another update as we have more information to share.
