Availability summary

GitHub experienced one incident in February that degraded availability for GitHub.com, issues, pull requests, GitHub Actions, and GitHub Codespaces.

February 2, 19:05–19:18 UTC

A routine deployment failed to produce the full set of integrity hashes required for Subresource Integrity. The output was missing values needed to securely serve JavaScript assets on GitHub.com.

GitHub's default safety behavior is to return an error rather than render script tags without integrity hashes. Because the hashes were missing from the integrity file, GitHub.com began serving 500 error pages to all browser-based users. The team detected the errors, rolled back to the previous deployment, and resolved the incident. API and Git access remained healthy throughout; only browser access to GitHub.com was affected.

What changed

In response, GitHub added the following safeguards:

  • Additional checks in the build process to verify integrity hashes are accurate and complete.
  • Checks for main JavaScript resources in the deployment container health check.
  • Adjustments to the build pipeline so integrity generation is more robust and less likely to fail the same way again.

The GitHub status page continues to provide the latest availability information.