CircleCI reported this major-impact incident on its official status page on Aug 17, 2026, 14:04 UTC. It was resolved after 5h 1m.
Right now CircleCI is operational. Live CircleCI status →
GitHub's APIs appear to be operating normally.
Some of GitHub's APIs are still degraded, resulting in a small number of failures relating to commit status updates and hook processing. We will continue to do our best to mitigate these effects.
GitHub API error rates and latencies appear to have recovered. We will continue to monitor.
We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.
We are continuing to see high error rates on GitHub's APIs and reduced webhook traffic. Customers using GitHub as their VCS may experience impact to their CircleCI platform experience as a result. This is directly linked to the incident GitHub is experiencing: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We will provide updates as more information becomes available.
We are continuing to see high error rates on GitHub APIs and reduced webhook traffic. We will continue to provide updates as more information becomes available.
GitHub has reported an incident that is impacting CircleCI pipeline triggering and logging in: https://www.githubstatus.com/incidents/zkxwbgr0cnmx Jobs that are in flights are running, but status reporting to GitHub Pull Requests may fail.
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