Minor impactResolvedDevOps

GitHub incident: Incident with CodeQL

GitHub reported this minor-impact incident on its official status page on May 13, 2026, 14:41 UTC. It was resolved after 1h 22m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 13, 2026, 14:41 UTC
started
May 13, 2026, 16:03 UTC
resolved
1h 22m
duration
Minor
impact
  1. resolvedMay 13, 2026, 16:03 UTC

    On May 13, 2026, between 14:31 and 16:03 UTC, the Code Scanning service experienced processing delays and 12% of check runs took over 15 minutes to complete. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues. We mitigated the impact by scaling our processing workers by 34%. Code Scanning results returned to normal processing times after the mitigation was applied. The capacity increases are permanent, and we are looking into more ways to decrease the load on our workers to help prevent this in the future.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on May 13, 2026: Incident with CodeQL · APIStatus.watch