https://approjects-vendor-status-watch.static.hf.space/v/circle-ci.htmlIncidents from Circle CI's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/0djh5p3ll96tcircle-ci:2026-09-15T14:42:25.100ZTue, 15 Sep 2026 14:42:25 +0000The incident impacting pipeline data in the UI has now been resolved. We thank you for your patience while our engineers worked on reducing the delays.https://stspg.io/d885vgdcmp7pcircle-ci:2026-09-14T11:59:15.782ZMon, 14 Sep 2026 11:59:15 +0000Wait times for macOS jobs are back to normal.https://stspg.io/l0tsrtv1tkblcircle-ci:2026-09-10T20:25:39.781ZThu, 10 Sep 2026 20:25:39 +0000This incident has been resolved. A small number of customers who created pipelines between 18:53 UTC and 19:24 UTC that contained config using deprecated config syntax will have seen their build-type jobs fail to start. Customers whose jobs or pipelines failed may rerun them.https://stspg.io/l8rtj1qhr625circle-ci:2026-09-04T15:16:02.197ZFri, 04 Sep 2026 15:16:02 +0000We've seen no further impact to queue times and everything has returned to normal. We appreciate your patience while we worked to resolve and monitor this issue.https://stspg.io/961zy5b9fnjkcircle-ci:2026-08-26T15:43:38.082ZWed, 26 Aug 2026 15:43:38 +0000This incident has been resolved.https://stspg.io/ns4jz57ynx52circle-ci:2026-08-25T20:00:00.000ZTue, 25 Aug 2026 20:00:00 +0000Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.https://stspg.io/gwc69d86r5sycircle-ci:2026-08-17T21:06:09.742ZMon, 17 Aug 2026 21:06:09 +0000Insights data is good once more. Thank you for your patience.https://stspg.io/mk4lvmlx939fcircle-ci:2026-08-17T14:04:21.229ZMon, 17 Aug 2026 14:04:21 +0000GitHub's APIs appear to be operating normally.https://stspg.io/v83b8dvfq3hqcircle-ci:2026-08-15T13:58:54.814ZSat, 15 Aug 2026 13:58:54 +0000Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced. Some customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC. This has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.https://stspg.io/5n5fpq53kkhhcircle-ci:2026-08-12T16:33:41.163ZWed, 12 Aug 2026 16:33:41 +0000The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.https://stspg.io/b811tvs48x2kcircle-ci:2026-08-11T17:42:47.509ZTue, 11 Aug 2026 17:42:47 +0000Between 13:50 UTC and approximately 17:30 UTC on August 11, 2026, some customers experienced delays of up to an hour in pipeline status updates and in notification delivery. Between 16:40 UTC and 17:00 UTC within that same window, a small number of customers also saw newly created pipelines fail to process, appearing in an errored state in the UI and API. The issue has been resolved and all affected functionality has returned to normal. Customers whose pipelines errored during that window can retrigger them. We thank you for your patience while our team worked on implementing a fix.https://stspg.io/kntq9cf4jgpkcircle-ci:2026-08-06T13:06:17.519ZThu, 06 Aug 2026 13:06:17 +0000The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.https://stspg.io/6qdzqdj5ww81circle-ci:2026-08-05T16:58:27.652ZWed, 05 Aug 2026 16:58:27 +0000The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.https://stspg.io/525771jb0gj4circle-ci:2026-08-04T19:27:28.000ZTue, 04 Aug 2026 19:27:28 +0000Queue times for Android and Windows jobs have reduced significantly over the last hour. You may still notice brief, isolated queuing at times, but this is no longer at incident-level impact. This was related to capacity constraints with a third-party infrastructure provider. We thank you for your patience while we monitored the situation. If you have any issues, please reach out to our Support team.https://stspg.io/8pvsx88khry9circle-ci:2026-07-24T16:35:44.272ZFri, 24 Jul 2026 16:35:44 +0000The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.https://stspg.io/jjsrf04jn924circle-ci:2026-07-22T19:57:15.421ZWed, 22 Jul 2026 19:57:15 +0000Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them. Unfortunately, workflows that we were unable to provision compute capacity for during this period were cancelled. Affected customers should change their resource class from gen3 to gen2 and rerun those workflows. We thank you for your patience while our team worked to resolve this.https://stspg.io/cw24pb57b6s9circle-ci:2026-07-22T06:13:48.941ZWed, 22 Jul 2026 06:13:48 +0000Between 03:18 UTC and 06:04 UTC on July 22, 2026, a subset of customers were unable to access app.circleci.com. The issue has been resolved and access has returned to normal. We thank you for your patience while our team worked on implementing a fix.https://stspg.io/96ffdz58cxdrcircle-ci:2026-07-20T00:35:59.020ZMon, 20 Jul 2026 00:35:59 +0000## Summary On July 20, 2026 from 00:22 to 01:45 UTC, CircleCI customers using our GitHub integrations experienced failures running pipelines and experienced workflows getting stuck. During this incident, some pipelines triggered by users using GitHub failed to start or ran as error pipelines. Customers whose pipelines failed or ran as error pipelines during this window should re-run them. This was caused by an [upstream API degradation at GitHub](https://www.githubstatus.com/incidents/ph5nns5y4gxj), which impacted many GitHub APIs that CircleCI uses to trigger and run pipelines. By 01:45 UTC, GitHub APIs recovered, and customer pipelines ran normally. The original CircleCI status page can be found [here](https://status.circleci.com/incidents/9lvbbbs9l87b).  ## What Happened \(all timhttps://stspg.io/jftpxjjgvqxycircle-ci:2026-07-16T23:04:18.952ZThu, 16 Jul 2026 23:04:18 +0000An incident affecting GitHub's API caused CircleCI customers to experience errors loading the web app and signing in, along with pipelines and scheduled workflows failing to start or running late. GitHub has resolved the underlying incident (https://www.githubstatus.com/) and all affected functionality has returned to normal. Customers whose jobs or pipelines failed may rerun them. Scheduled pipelines and workflows that were missed during the incident will not run automatically and will need to be re-triggered. We thank you for your patience.https://stspg.io/0t40l14n15ylcircle-ci:2026-07-14T22:54:42.726ZTue, 14 Jul 2026 22:54:42 +0000On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. The same issue recurred on July 14 between 15:45 UTC and 22:50 UTC. Delays reached up to 25 minutes on July 13 and up to 24 minutes on July 14. The medium+ and 2 X-large+ resource classes saw the longest waits. Earlier updates in this incident reported figures based on average wait times, which didn't reflect the maximum impact some customers may have experienced. Wait times have now returned to normal. We are continuing to work with our cloud provider to add capacity ahead of the next peak period. Thank you for your patience.https://stspg.io/lzl0fmm6xmtscircle-ci:2026-07-14T02:49:37.834ZTue, 14 Jul 2026 02:49:37 +0000## Summary From 01:33 UTC to 05:18 UTC on July 14, 2026, customers with a Bitbucket-linked identity were unable to log in to CircleCI, and some customers experienced workflows that failed to start or update, due to a change in how Bitbucket's OAuth service reports account permissions. At 05:07 UTC, we deployed a fix that corrected how our systems read the updated permissions field. Some customers needed to log out and re-authenticate their Bitbucket integration after we deployed the fix. Our systems continued processing the backlog of affected jobs until 08:39 UTC. We thank our customers for their patience as we resolved this incident. Please reach out to our support team with any questions or concerns. The status page for this incident can be found [here](https://status.circleci.com/inhttps://stspg.io/vg35mbl8lxpgcircle-ci:2026-07-13T21:52:02.888ZMon, 13 Jul 2026 21:52:02 +0000## Summary From 18:00 UTC on July 13, 2026 to 23:18 UTC on July 14, 2026, some customers running jobs on CircleCI's macOS fleet experienced jobs that hung or failed to progress during GitHub fetch steps. For these customers, GitHub fetch steps which would ordinarily take 1-2 minutes took 20-30 minutes, and timed out. The issue was caused by a capacity and routing problem on the network path between our Mac infrastructure provider and GitHub, and the associated intermittent networking issues slowed down fetches from GitHub. During the entire incident, our team worked directly with our Mac infrastructure provider to identify and reroute traffic away from the affected network paths. We resolved an initial occurrence at 19:40 UTC on July 13. The issue recurred at 21:52 UTC that same day, we rhttps://stspg.io/vc3sdl5vsqyrcircle-ci:2026-07-13T18:55:54.301ZMon, 13 Jul 2026 18:55:54 +0000We've confirmed the fix with our infrastructure provider and successful tests on our end. If customers continue to see any failed runs, please run again for a successful connection and reach out to Support if any further issues.https://stspg.io/n86hwbb1whpccircle-ci:2026-07-02T15:25:28.360ZThu, 02 Jul 2026 15:25:28 +0000## Summary On July 2, 2026, from 15:12 UTC to 16:44 UTC, some CircleCI customers experienced failures starting pipelines and difficulty accessing the CircleCI UI, including an inability to log in. Customers triggering pipelines via the API may also have had pipelines fail to run. The incident originated from a combination of internal maintenance and customer-initiated project deletions running concurrently, which caused elevated load on a data service. The connection layer between our API and that data service was not configured to time out slow responses under the elevated load conditions seen during this incident. This eventually exhausted available threads and prevented the request routing layer from handling any other requests, resulting in customer-facing errors. The affected servihttps://stspg.io/ty6ll6xj9c18circle-ci:2026-06-29T10:23:34.607ZMon, 29 Jun 2026 10:23:34 +0000This incident has been resolved.https://stspg.io/z1sdwdk27983circle-ci:2026-06-26T15:00:00.000ZFri, 26 Jun 2026 15:00:00 +0000We observed a surge in demand for Xcode 26.6 and have since mitigated the incident by increasing the available capacity for that Xcode version. Customers may have seen jobs queueing for ~10-15 mins.https://stspg.io/0hqc49q254gdcircle-ci:2026-06-25T22:44:15.737ZThu, 25 Jun 2026 22:44:15 +0000This incident has been resolved.https://stspg.io/mrq29l3fw2cmcircle-ci:2026-06-24T23:13:45.020ZWed, 24 Jun 2026 23:13:45 +0000We are concluding this incident based on a confirmed fix with our infrastructure provider and successful tests. For any customers seeing failed runs, please run again for a successful connection.https://stspg.io/dw1r4sr0mrtlcircle-ci:2026-06-23T18:34:35.096ZTue, 23 Jun 2026 18:34:35 +0000## Summary On Tuesday, June 23, 2026, our engineering team identified that a single Docker job cluster was operating below expected performance levels. Our infrastructure is organized into routing groups, each responsible for handling a specific segment of traffic, and this cluster was the sole member of its group. To address the performance issue, they initiated a standard two-step procedure to safely take it out of rotation: first, update the routing configuration to stop directing traffic to the cluster, then take it offline. When the team moved to take the cluster offline, the first step of the procedure was skipped. The cluster was removed from the available pool, but the routing configuration was not updated, meaning traffic continued to be directed to the routing group even thoughhttps://stspg.io/qjt275qv8plhcircle-ci:2026-06-11T21:31:49.306ZThu, 11 Jun 2026 21:31:49 +0000Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.