Partial degradation for code scanning default setup and for code quality
Incident
Report for GitHub
Resolved
On April 20, 2026 between 10:28 UTC and 15:04 UTC GitHub experienced degraded service for code scanning default setup, code quality, and project boards. Repair of affected project boards additionally lasted until April 21, 05:04 UTC
During this time, code scanning default setup and code quality analyses were not triggered on newly opened pull requests. Additionally, newly created issues were not appearing on project boards.
The cause was a serialization error that prevented proper triggering of code scanning, code quality analyses, and project board updates.
We mitigated the issue by deploying a fix, restoring event publishing for code scanning and code quality. For project boards, an additional code change was deployed to update event consumers, followed by a reindex of affected project items.
We are working to prevent recurrence by strengthening our schema validations and improving monitoring for drops in publishing on critical hydro topics.
During this time, code scanning default setup and code quality analyses were not triggered on newly opened pull requests. Additionally, newly created issues were not appearing on project boards.
The cause was a serialization error that prevented proper triggering of code scanning, code quality analyses, and project board updates.
We mitigated the issue by deploying a fix, restoring event publishing for code scanning and code quality. For project boards, an additional code change was deployed to update event consumers, followed by a reindex of affected project items.
We are working to prevent recurrence by strengthening our schema validations and improving monitoring for drops in publishing on critical hydro topics.
Update
The degradation has been mitigated. We are monitoring to ensure stability.
Update
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.
Update
The degradation has been mitigated. We are monitoring to ensure stability.
Update
The degradation has been mitigated. We are monitoring to ensure stability.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Update
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.
Update
A deployment to fix this issue of new issues not showing up in projects is underway.
Update
We continue to work on mitigation regarding new issues not showing on project boards.
Update
We continue to work on mitigation regarding new issues not showing on project boards.
Update
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.
We are seeing problems with new issues not showing on project boards and are working on mitigation.
Update
We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.
Update
We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.
Update
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.
Investigating
We are investigating reports of impacted performance for some GitHub services.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe