Live  /  CircleCI  /  Incident

CircleCI: Delays for gen2 dedicated IP range jobs

CircleCI · circleci.comMinor incidentResolved2026-10-28 19:19 UTC
Public — what happened

Summary

CircleCI said that starting at 18:15 UTC on 2026-10-28, Docker gen2 jobs using dedicated IP ranges were delayed by about 10 minutes, and that no other resource classes were affected. By 18:51 UTC the company said it had identified the cause as limited computing capacity from its cloud provider, and that it was working to free up more capacity. At 19:06 UTC CircleCI reported wait times beginning to return to normal, and the incident was marked resolved at 19:19.

Affected

Docker Jobs

As listed on CircleCI’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach CircleCI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for CircleCI: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the CircleCI report →

More from CircleCI

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the CircleCI status & history page.

Related: CircleCI status & history. SquidGrid is not affiliated with CircleCI.