--- service: "Circle CI" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T03:49:35.540Z" url: "https://instatus.com/now/zh/circleci.com" official_status_page: "https://status.circleci.com" website: "https://circleci.com" --- # Circle CI 故障了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ## 官方更新 - **Delays for gen2 dedicated IP range jobs** (RESOLVED, 2026-10-28T18:15:52.000Z): ## **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/8q9j33r2rssy). ## **Background** IP Ranges is a CircleCI feature that runs jobs from a published static list of IP addresses, so customers can configure their firewalls to allow those addresses. Gen 2 Docker jobs using IP Ranges need to run on their own dedicated cluster of cloud instances, separate from our other Gen 2 Docker jobs. Customers rely on the published IP address list, so we give 30 days’ notice before adding new IP addresses. Because of that notice period, we cannot move IP Ranges jobs to a new cloud region on short notice. When CircleCI runs a Docker job, we schedule it on one of several clusters of cloud instances, and each instance can run multiple isolated jobs. We provision cloud instances using a ranked list of instance types. If the cloud provider cannot supply our first choice, we fall back to the next type on the list. Each request tries our preferred types first, so when several of them are unavailable, each request takes longer and the cluster grows more slowly. We also maintain a minimum fleet size: a minimum number of instances that stay running, so that capacity is ready before demand arrives. Above that minimum, we add instances as demand rises. When there is insufficient capacity to run a job, the job waits in a queue until capacity becomes available. ## **What Happened** _\(All times UTC\)_ Starting at 14:20 on October 28, Gen 2 Docker jobs using IP Ranges saw intermittent delays because the instance types we had configured for the IP Ranges cluster were not available in the quantities we needed. Wait times rose to 5 minutes and then returned to normal several times until 17:02. From 17:02, the delays were continuous. Our wait time alerts did not specifically isolate IP Ranges jobs, so these delays did not immediately alert our engineering team. At 17:22, our engineering team began investigating and confirmed that the IP Ranges cluster could not provision sufficient instances. An unrelated incident at our observability provider from 16:10 to 18:39 also slowed our investigation by affecting dashboards and metric queries. Following the [October 21 incident](https://discuss.circleci.com/t/post-incident-report-oct-21-2026-increased-wait-times-for-gen-2-docker-jobs/54940), we added fallback instance types and additional cloud regions for our main Gen 2 clusters, but the IP Ranges cluster had not yet received those changes. Our engineering team had scheduled work for October 30 to configure the IP Ranges cluster with additional fallback instance types, but that work had not begun at the time of this incident. Because of the 30-day notice, we could not immediately move IP Ranges jobs to another region, so our engineering team reallocated capacity from other CircleCI clusters in the same region. By 18:50, the IP Ranges cluster had provisioned sufficient instances, and wait times began returning to normal. Delays of 1-2 minutes continued until 19:08. We resolved the incident at 19:19. ## **Future Prevention and Process Improvement** **We raised the minimum fleet size for the IP Ranges cluster.** We now keep more cloud instances running for IP Ranges jobs during weekday peak hours. This means capacity is in place before demand arrives, and we do not depend on the cloud provider supplying instances during an increase in demand. **We have added an additional region for IP Ranges jobs.** We have set up dedicated IP Ranges clusters for Gen 1 and Gen 2 in a second cloud region, so they will be able to run jobs as soon as the 30 day notice period ends. During that notice period, the higher minimum fleet size and the expanded list of fallback instance types protect IP Ranges jobs in our current region. **We are expanding our alerting.** We are adding more targeted wait time alerts specifically for IP Ranges jobs, so our team can respond immediately to delays. ## **Conclusion** Customer experience is our top priority, and we commit to continually improving the reliability of our systems to match the trust that our customers place in us. We thank our customers for their patience while our team worked to resolve this incident. Please reach out to our support team with any questions or concerns. ## Circle CI 故障常见问题 ### Circle CI 现在挂了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ### Circle CI 是所有人都坏了，还是只有我？ 看起来只有你遇到。Circle CI 的反馈量正常，可以试试刷新页面、检查网络连接，或退出后重新登录。 ### 大家反馈了 Circle CI 的哪些问题？ 过去一小时内没有人说明 Circle CI 哪里坏了。如果你遇到问题，请在上方选择，让其他人看到。 ### Circle CI 上次故障是什么时候？ 过去 30 天内，Circle CI 的反馈没有出现激增。 ### Circle CI 有状态页面吗？ 有。Circle CI 会在官方状态页面发布更新，目前显示：运行正常。 [前往状态页面](https://status.circleci.com/) ### Circle CI 无法使用时我可以怎么办？ 查看本页和 Circle CI 的状态页面获取更新，等几分钟再试一次。不用重新安装：如果是服务中断，要由他们那边修复。 ### 如何反馈 Circle CI 的问题？ 点击本页顶部的“我也要反馈问题”，再选择哪里坏了。你的反馈会在一分钟内显示在实时图表上，也可以留言告诉其他人你遇到的情况。 ### Instatus Now 是怎么知道的？ 我们把此页面上用户的反馈，与每分钟检查一次的 Circle CI 官方状态页结合起来。