CircleCI incident: Delays for gen2 dedicated IP range jobs

Affected components

• Docker Jobs

1. postmortemOct 31, 2026, 00:22 UTC

   ## **Summary** From 14:20 to 19:08 UTC on October 28, customers running Gen 2 Docker jobs using IP Ranges saw increased wait times for their jobs to start. From 14:20 until 17:02, the delays were intermittent, and from 17:02 to 18:50, the delays were continuous. No other job types were affected. The incident was caused by limited availability of the cloud instances we had configured for the IP Ranges cluster. In response, our engineering team added additional fallback instance types to the IP Ranges cluster and transferred capacity from one of our other Gen 2 clusters to the IP Ranges cluster. By 18:50, wait times had improved, and by 19:08 they had fully recovered. After we resolved the incident, we increased the number of baseline cloud instances we maintain for IP Ranges jobs. We have also configured an IP Ranges cluster in an additional cloud region. The original status page can be found here: [Delays for gen2 dedicated IP range jobs](https://status.circleci.com/incidents/8q9j3

2. resolvedOct 28, 2026, 19:19 UTC

   Wait times for gen2 dedicated IP range jobs have fully returned to normal. We appreciate your patience while worked through this issue.

3. monitoringOct 28, 2026, 19:06 UTC

   We are starting to see signs of recovery now, wait times are starting to return to normal. We're keeping an eye on this and we'll update again soon.

4. identifiedOct 28, 2026, 18:51 UTC

   We’ve identified the cause as limited compute availability from our cloud provider, and we are working to free up additional capacity for these jobs to restore normal start times. We'll provide another update again shortly.

5. investigatingOct 28, 2026, 18:15 UTC

   We are investigating delays in starting docker gen2 jobs that use dedicated IP ranges. Jobs are currently delayed by about 10 minutes. No other resource classes are impacted at this time. We will continue to provide updates as more information is available.

What APIStatus.watch saw

• Oct 28, 2026, 18:19 UTCoperational → degraded
• Oct 28, 2026, 19:24 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Datadog: Metrics query are disruptedMajor · Oct 28, 2026, 16:10 UTC
• Akamai: Edge Delivery issues between Indonesia and SingaporeMinor · Oct 25, 2026, 13:44 UTC
• Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)Minor · Oct 25, 2026, 13:54 UTC
• Cloudflare: Cloudflare Pages Upload IssueMinor · Oct 26, 2026, 00:00 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Digi Mobil RomaniaMinor · Oct 26, 2026, 13:09 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Short Codes to Docomo Pacific United StatesMinor · Oct 26, 2026, 20:57 UTC
• Twilio: SMS Delivery Failures From a Subset of Twilio Phone Numbers to Multiple Networks in BrazilMinor · Oct 26, 2026, 23:55 UTC
• Twilio: Voice Call Failures From Twilio Phone Numbers to GermanyMinor · Oct 27, 2026, 09:00 UTC
• Tailscale: Funnel hostnames not resolving in public DNSMinor · Oct 27, 2026, 14:16 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to C-Spire United StatesMinor · Oct 27, 2026, 21:31 UTC

How often does CircleCI have incidents?

CircleCI reported 23 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 12m. See CircleCI's uptime and incident history