Live status · checked every 15 minutes
Is CircleCI down right now?
CircleCI runs continuous integration and delivery pipelines for software teams.
Live reader reports
Is CircleCI down for you?
Tap what's not working, or tell us it works. Reports are anonymous, one per visitor.
No reports in the last 24 hours. Be the first to tell other readers what you're seeing.
CircleCI not working for you?
- Check your internet connection and any VPN or corporate proxy.
- Sign out and back in, or try a private browser window.
- Check the specific feature you use on the official status page: one part can be down while the rest works.
- Retry failed API calls and jobs with backoff.
CircleCI outage history
Last 30 daysFixed Delays and intermittent failures running Smarter Testing
Affected: Docker Jobs, Machine Jobs, macOS Jobs, Windows Jobs
-
Smarter Testing functionality is restored. We appreciate your patience as we worked through this.
-
The maintenance was successful. Smarter Testing functionality has been restored. We are monitoring to ensure performance remains stable.
-
At 18:45 UTC, we will perform emergency maintenance, which is expected to take a few minutes. During this window, test jobs for customers using Smarter Testing may be delayed or fail. Thank you for your patience while our engineers work to resolve this. We will provide another update by 19:05 UTC.
-
Since 17:55 UTC, test jobs for customers using Smarter Testing have been running again. Dynamic Test Splitting is still not running optimally. Dynamic Parallelism is also not running optimally, so jobs that use it should be expected to fall back to using all nodes. Thank you for your patience while our engineers work to resolve this. We will provide another update by 18:50 UTC
-
Since 17:55 UTC, test jobs for customers using Smarter Testing have been running again. Dynamic Test Splitting is still not running optimally. Dynamic Parallelism is also not running optimally, so jobs that use it should be expected to fall back to using all nodes. Thank you for your patience while our engineers work to resolve this. We will provide another update by 18:30 UTC.
-
Since 17:38 UTC, some test jobs for customers using Smarter Testing have been failing. Thank you for your patience while our engineers work to resolve this.
-
Since 17:09 UTC, we have been seeing delays in updating test impact analysis data. Test selection may be less precise, which may cause more tests than necessary to run. Thank you for your patience while our engineers work to resolve this.
-
Starting at 16:38 UTC, test jobs for customers using Smarter Testing should be back running. Dynamic Test Splitting may still not be working optimally for some customers.
-
Some Smarter Testing customers may not be able to run tests. We are also seeing delays updating the impact analysis data map, which may cause more tests to be selected by Smarter Testing.
Fixed Increased wait time for Machine and Remote Docker jobs
Affected: Machine Jobs
-
## Summary From 13:55 to 15:07 UTC on November 3, customers running Linux machine jobs and Remote Docker saw increased wait times for their jobs to start, and the delays were longest from 14:16 to 14:41. Some Docker jobs also saw increased wait times. The incident was caused by our usage reaching the vCPU limit on our cloud provider account in our main cloud region. Machine and Docker jobs share this limit, and the additional Docker capacity we have run since the [October 21 incident](https://discuss.circleci.com/t/post-incident-report-oct-21-2026-increased-wait-times-for-gen-2-docker-jobs/54940) brought our usage to the limit as demand increased. Machine jobs did not move to our backup regions because our system did not treat reaching this limit the same way as a shortage of cloud instances. In response, our engineering team reconfigured machine jobs to balance across all of our regions instead of relying on backup regions, and reduced Docker capacity to make room under the limit. By 14:46, wait times had improved, and by 15:07, machine wait times had fully recovered. After we resolved the incident, our cloud provider doubled the vCPU limit in our main region. We have also restored the Docker capacity we reduced during the incident. The original status page can be found here: [Increased wait time for Machine and Remote Docker jobs](https://status.circleci.com/incidents/qqh50c0z6mn3). ## Background Machine jobs need a dedicated virtual machine, so when CircleCI runs a machine job, we create a fresh virtual machine for that job and delete it when the job ends. Remote Docker runs on these same virtual machines. Docker jobs run on shared cloud instances, and each instance can run multiple isolated jobs. Our cloud provider sets a vCPU limit for each region, which caps the total computing capacity our account can run there. Machine and Docker jobs run in the same account, so they count against the same vCPU limit. When our usage reaches that limit, the cloud provider re…
-
Wait times have returned to normal for Machine and Remote Docker. We appreciate your patience as we worked through this.
-
Our team has applied a fix and we're starting to see wait times recover. We're keeping an eye on this as it continues to rollout and we'll update again shortly. We thank you again for your patience.
-
Some users might see increased wait times for Machine and Remote Docker jobs due to increased usage. Wait times right now are just under 7 mins. Our team is investigating and we'll post another update shortly. We appreciate your patience.
Fixed Delays for gen2 dedicated IP range jobs
Affected: Docker Jobs
-
## **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…
-
Wait times for gen2 dedicated IP range jobs have fully returned to normal. We appreciate your patience while worked through this issue.
-
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.
-
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.
-
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.
Fixed Increased Docker gen2 wait times
Affected: Docker Jobs
-
## Summary From 15:44 to 20:55 UTC on October 21, customers running Gen 2 Docker jobs saw increased wait times for their jobs to start. Delays were longest on the 2xlarge resource class, where jobs waited up to 20 minutes. The incident was caused by limited availability of the cloud instances we had configured to meet demand, particularly for 2xlarge jobs. In response, our engineering team configured additional instance types, configured additional Gen 2 Docker clusters. By 20:55 UTC, wait times had returned to normal and the incident was resolved. After the incident was resolved, we expanded our Gen 2 Docker fleet into additional cloud regions, and we continue actively standing up additional cloud regions to prevent similar incidents in the future. The original status page can be found here: [October 21 - Increased Docker gen2 wait times](https://status.circleci.com/incidents/5jb50gh55gtj). ## Background When CircleCI executes a Docker job, we schedule it on one of several clusters of cloud instances, and each instance is capable of executing multiple isolated jobs. Scheduling a job on a cloud instance is a classic [“bin packing problem”](https://en.wikipedia.org/wiki/Bin_packing_problem): finding available capacity that fits the requested resource class’ CPU, memory, and storage. Larger resource classes like 2xlarge are harder to fit than smaller ones, which pack together more tightly. 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. We further maintain a minimum fleet size: a minimum number of instances stay running, so that we do not give up capacity when demand is low. Above that minimum fleet size, we add instances as demand rises. When there is insufficient capacity to execute a workload, we queue that work until capacity becomes available. ## What Happened _\(All times UTC\)_ Starting at 15:44 on October 21, demand for the Gen 2 2xlarge resour…
-
Wait times for gen2 Docker jobs have recovered and jobs are running within normal wait times.
-
We have seen a full recovery of wait times for docker jobs.
-
Wait times for 2xlarge docker jobs are now under 60 seconds. Wait times for other resource sizes were not impacted by this incident and remain under 10 seconds.
-
Wait times for 2xlarge docker jobs are recovering. We will continue to update as capacity comes online.
-
We are adding additional capacity to help mitigate the issue. Note: We are still seeing delays up to 20 minutes on 2xlarge.
-
Some users might see increased wait times for gen2 Docker jobs due to capacity issues.
Frequently asked questions
Is CircleCI down right now?
No. As of 20:15 UTC on 19 November 2026, CircleCI is working normally. If it is not working for you, try the checklist on this page.
When was the last CircleCI outage?
The last incident was "Delays and intermittent failures running Smarter Testing" on 19 November 2026, fixed after 51 minutes 35 seconds.
Why is CircleCI not working for me?
If this page shows no problem and few readers report one, the cause is usually local: your connection, a VPN or firewall, an outdated app or a sign-in problem. Work through the checklist above, then report it here so other readers can see it.
Unofficial status page. Teczpert is not affiliated with CircleCI. Status data comes from the official status page and is checked every 15 minutes; reports come from readers. Official source: status.circleci.com.