Major incident

CircleCI: GitHub Incidents impacting CircleCI functionality

Current status of CircleCI: Operational — live CircleCI status

Timeline

1. Aug 17, 2026, 14:04 UTC
   identified
   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.
2. Aug 17, 2026, 14:25 UTC
   identified
   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.
3. Aug 17, 2026, 15:49 UTC
   identified
   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.
4. Aug 17, 2026, 16:22 UTC
   monitoring
   We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.
5. Aug 17, 2026, 17:01 UTC
   monitoring
   GitHub API error rates and latencies appear to have recovered. We will continue to monitor.
6. Aug 17, 2026, 17:23 UTC
   monitoring
   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.
7. Aug 17, 2026, 19:05 UTC
   resolved
   GitHub's APIs appear to be operating normally.

Updates as published by CircleCI (original).