Partial degradation for code scanning default setup and for code quality

Update timeline

1. investigating Apr 20, 2026, 01:28 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Apr 20, 2026, 01:57 PM UTC

   We are actively working to mitigate an issue affecting code scanning default setup and code quality features on pull requests. Users may experience pull request code scanning and code quality analyses not being triggered on new pull requests. Our engineering team has identified the root cause and working on mitigating the issue.

3. investigating Apr 20, 2026, 02:38 PM UTC

   We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.

4. investigating Apr 20, 2026, 03:20 PM UTC

   We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.

5. investigating Apr 20, 2026, 04:16 PM UTC

   Code scanning default setup and Code Quality triggers are back up and running. PRs not processed before or during this incident will require a new push to trigger code scanning or code quality analysis. We are seeing problems with new issues not showing on project boards and are working on mitigation.

6. investigating Apr 20, 2026, 04:48 PM UTC

   We continue to work on mitigation regarding new issues not showing on project boards.

7. investigating Apr 20, 2026, 05:32 PM UTC

   We continue to work on mitigation regarding new issues not showing on project boards.

8. investigating Apr 20, 2026, 06:08 PM UTC

   A deployment to fix this issue of new issues not showing up in projects is underway.

9. investigating Apr 20, 2026, 06:20 PM UTC

   The issue has been mitigated. Newly created issues linked to projects should now function as expected. Issues that were linked to projects during the incident may take approximately five hours to render correctly while we complete a re-index.

10. monitoring Apr 20, 2026, 06:20 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

11. monitoring Apr 20, 2026, 06:21 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

12. monitoring Apr 20, 2026, 09:36 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

13. monitoring Apr 21, 2026, 03:10 AM UTC

    The issue remains mitigated. Issues that were linked to projects during the incident may take approximately three more hours to render correctly while we complete a re-index.

14. monitoring Apr 21, 2026, 04:18 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

15. resolved Apr 21, 2026, 05:04 AM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.