Outage impacting web experience and pipelines starting

Final update

## 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 services were scaled up and the internal maintenance job was canceled to reduce pressure, allowing all affected functionality to return to normal. Customers whose jobs failed during this window may rerun affected jobs. A small number of customers may still see workflows that appear to be running; this is actively being corrected and does not impact billing. We thank you for your patience while our team wo

1. Postmortem · Jul 10, 18:57 UTC
   ## 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 services were scaled up and the internal maintenance job was canceled to reduce pressure, allowing all affected functionality to return to normal. Customers whose jobs failed during this window may rerun affected jobs. A small number of customers may still see workflows that appear to be running; this is actively being corrected and does not impact billing. We thank you for your patience while our team worked on implementing a fix. ## What Happened \(all times UTC\) At 13:30 on July 2, 2026, as part of normal platform maintenance, our engineering team began a data deletion job, divided into several hundred individual maintenance tasks. At 14:40, unrelated to our platform maintenance, a significant n
2. Resolved · Jul 2, 16:44 UTC
   Pipelines and UI access have fully recovered. Please contact customer support if you have issues running builds. This incident has been resolved.
3. Monitoring · Jul 2, 16:29 UTC
   Pipelines are continuing to run as normal. We will continue monitoring for recovery.
4. Monitoring · Jul 2, 16:24 UTC
   We have identified a source of increased system load which caused failures processing API requests. We have mitigated the issue and jobs are now running as expected and UI access has recovered. Some pipelines may have failed or failed to start. Resubmitting should correct these issues. We are continuing to monitor to ensure recovery.
5. Investigating · Jul 2, 16:07 UTC
   We are investigating an issue that may cause some customers to be redirected to a login page and prevents some pipelines from starting. Thank you for your patience as we continue our mitigation of this issue.
6. Investigating · Jul 2, 15:25 UTC
   We are currently investigating this issue.