--- service: "Circle CI" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T06:42:59.551Z" url: "https://instatus.com/now/ko/circleci.com" official_status_page: "https://status.circleci.com" website: "https://circleci.com" --- # Circle CI 다운되었나요? 아니요, 정상이에요. 최근 1시간 동안 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 장애 FAQ ### 지금 Circle CI 다운됐나요? 아니요, 정상이에요. 최근 1시간 동안 0건 보고됨. ### Circle CI이(가) 모두에게 안 되나요, 저만 안 되나요? 당신만 겪는 문제일 수 있어요. Circle CI 제보가 평소 수준이니, 페이지를 새로고침하거나 연결을 확인하거나 로그아웃 후 다시 로그인해 보세요. ### Circle CI에서 사람들은 어떤 문제를 제보하나요? 지난 1시간 동안 Circle CI에서 무엇이 안 되는지 말한 사람이 없습니다. 안 되는 게 있다면 위에서 선택해 다른 사람들도 볼 수 있게 해주세요. ### Circle CI의 마지막 장애는 언제였나요? Circle CI 제보는 최근 30일간 급증하지 않았어요. ### Circle CI에 상태 페이지가 있나요? 네. Circle CI은(는) 공식 상태 페이지에 업데이트를 올리며, 현재 상태는 정상입니다. [상태 페이지로 이동](https://status.circleci.com/) ### Circle CI이(가) 안 되면 어떻게 하나요? 이 페이지와 Circle CI의 상태 페이지에서 업데이트를 확인하고, 몇 분 기다린 후 다시 시도하세요. 재설치는 하지 마세요. 장애라면 해결은 서비스 쪽에서 합니다. ### Circle CI 문제는 어떻게 제보하나요? 이 페이지 상단의 “저도 같은 문제가 있습니다”를 누르고 무엇이 안 되는지 선택하세요. 제보는 1분 안에 실시간 차트에 표시되며, 댓글로 어떤 상황인지 다른 사람에게 알려줄 수도 있습니다. ### Instatus Now는 어떻게 알죠? 이 페이지의 사용자 제보와 매분 확인하는 Circle CI 공식 상태 페이지를 함께 살펴봐요.