In February, GitHub experienced one significant incident.
February 2 Incident (19:05 UTC, lasting 13 minutes)
A deployment error caused widespread service degradation affecting GitHub.com, issues, pull requests, GitHub Actions, and GitHub Codespaces. Browser users encountered 500 error pages site-wide. Browser-based access was affected; API and Git access remained operational.
Root Cause: The deployment failed to generate complete Subresource Integrity (SRI) hashes required for secure JavaScript asset delivery. Per safety protocols, GitHub’s system defaults to erroring rather than serving unverified scripts, causing all web traffic to fail.
Resolution: Engineers immediately rolled back to the previous deployment, restoring service.
Preventive Measures: GitHub implemented additional build process checks for integrity hash accuracy, added health checks for main JavaScript resources in deployment containers, and enhanced robustness in the integrity generation pipeline to prevent similar failures.
Tags
Only on this entry: integrity-check