CircleCI reported this minor-impact incident on its official status page on Jul 20, 2026, 00:35 UTC. It was resolved after 1h 10m.
Right now CircleCI is operational. Live CircleCI status →
## 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 times UTC\) Beginning 00:22 on July 20, 2026, GitHub began returning elevated errors for the following API requests: * `applications/*/token` * `repos/*/commits` * `repos/*/*/contents/*` * `repos/*/*/h
GitHub API error rates have recovered to normal levels. During the incident, some customers may have seen pipelines fail to start or not receive status updates. Some pipelines may be stuck in a running state. * You should re-push commits or use the UI to manually trigger pipelines that didn't start. * Pipelines in a stuck running state should be canceled and rerun. If you encounter any issues please contact CircleCI support.
We are seeing signs of recovery from the GitHub API. We will stay in a monitoring state to verify that the API error rate has recovered.
We are also seeing errors processing push event webhooks due to the upstream API outage. Users may need to retry pipelines for these push events.
We have identified an issue with GitHub API requests that may cause some customers to see workflows stuck in a running state or workflows fail to start. GitHub has reported incidents on the APIs https://www.githubstatus.com/incidents/ph5nns5y4gxj https://www.githubstatus.com/incidents/8vfyvq16hzh9 We are monitoring the stability of GitHub APIs and will update this page as more information is available.
Our 5-minute checks didn't record a change in CircleCI's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
CircleCI reported 22 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 38m. See CircleCI's uptime and incident history