Circle CI incident

GitHub Incidents impacting CircleCI functionality

Major Resolved View vendor source →

Circle CI experienced a major incident on August 17, 2026, lasting 5h 1m. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 02:04 PM UTC
Resolved
Aug 17, 2026, 07:05 PM UTC
Duration
5h 1m
Detected by Pingoru
Aug 17, 2026, 02:04 PM UTC

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. monitoring Aug 17, 2026, 05:01 PM UTC

    GitHub API error rates and latencies appear to have recovered. We will continue to monitor.

  6. 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.

  7. resolved Aug 17, 2026, 07:05 PM UTC

    GitHub's APIs appear to be operating normally.