GitHub Service Degradation: Code Scanning and Project Boards Affected (April 20-21, 2026)
By
SenHeng
A good honest bake. Not flashy, but you'll finish the whole bagel.
Summary
GitHub experienced a service degradation on April 20-21, 2026, affecting code scanning default setup, code quality analyses, and project boards. The issue lasted approximately 4.5 hours for most services, with project board repairs extending an additional 14 hours. The root cause was a serialization error that prevented proper triggering of these features. During the incident, code scanning and code quality analyses were not triggered on new pull requests, and newly created issues did not appear on project boards.
Key quotes
· 4 pulledOn 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.
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.
You might also wanna read
GitHub Actions suffers three-hour outage with false 'account suspended' error
GitHub Actions experienced a major outage lasting over three hours, during which users saw an alarming but incorrect error message stating "
theregister.com·2d ago
GitHub patches critical remote code execution vulnerability in under six hours after AI-assisted discovery
GitHub patched a critical remote code execution vulnerability in under six hours last month. The flaw, discovered by Wiz Research using AI m
The Verge·1mo ago