Resolved after 5 hours 1 minute, on August 17, 2026.
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.
Update timeline
- identified Aug 17, 2026, 02:04 PM UTC
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.
- identified Aug 17, 2026, 02:25 PM UTC
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.
- identified Aug 17, 2026, 03:49 PM UTC
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.
- monitoring Aug 17, 2026, 04:22 PM UTC
We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.
- monitoring Aug 17, 2026, 05:01 PM UTC
GitHub API error rates and latencies appear to have recovered. We will continue to monitor.
- monitoring Aug 17, 2026, 05:23 PM UTC
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.
- resolved Aug 17, 2026, 07:05 PM UTC
GitHub's APIs appear to be operating normally.
Your product runs on more than Circle CI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services