GitHub Incidents impacting CircleCI functionality

Timeline

1. 14:04 UTC CircleCI status page · Reported GitHub Incidents impacting CircleCI functionality
2. 14:04 UTC CircleCI status page · 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.
3. 14:25 UTC CircleCI status page · 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.
4. 15:49 UTC CircleCI status page · 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.
5. 16:22 UTC CircleCI status page · Monitoring We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.
6. 17:01 UTC CircleCI status page · Monitoring GitHub API error rates and latencies appear to have recovered. We will continue to monitor.
7. 17:23 UTC CircleCI status page · 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.
8. 19:05 UTC CircleCI status page · Resolved GitHub's APIs appear to be operating normally.