Live › incident › INC-circleci-9lvbbbs9l87b
Go to dashboardCircleCI had an incident from July 20, 2026 00:22 to 01:45 UTC where pipelines using GitHub integrations failed to start, ran as error pipelines, or got stuck. The cause was an upstream GitHub API degradation, and the incident is resolved.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| CircleCI | vendor | – | – |
Check pipelines triggered by GitHub during 00:22 to 01:45 UTC on July 20, 2026 for failed, error or stuck status.
Re-run any pipelines that failed or ran as error pipelines during the incident window, as CircleCI advises.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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, 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.
(all times UTC)
Beginning 00:22 on July 20, 2026, GitHub began returning elevated errors for the following API requests:
applications/*/tokenrepos/*/commitsrepos/*/*/contents/*repos/*/*/hooksrepos/*/*/hooks/*repos/*/*/keysrepos/*/*/pullsrepos/*/*/statuses/*CircleCI relies on these requests to correctly trigger and run pipelines.
At 00:22, our internal monitoring alerted us to the problem. Our team began investigating, and found that a small number of pipelines belonging to GitHub projects either failed to start or ran as error pipelines. This included scheduled pipelines and workflows. In addition, a small number of customer workflows experienced stuck jobs and required a re-run of the workflow to fix.
At 01:45, GitHub recovered and pipeline processing returned to normal operating levels. Only pipelines triggered during the incident window were affected, and customers should re-run those pipelines.
We are actively working to improve the resilience of pipeline processing during GitHub service disruptions to reduce the customer impact of similar incidents in the future. We are scoping features that will help customers recover with reduced manual steps after incidents resolve.
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. Please reach out to our support team with any questions or concerns.
This page as .md · .json · in your agent: get_signal("INC-circleci-9lvbbbs9l87b")