Provider
GitHubIncident detail
Incident with CodeQL
Resolved incidentMinor
Timeline window
to
Outage alerts
Get alerted the next time GitHub breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update GitHub posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
We are investigating reports of impacted performance for some GitHub services.
Investigating
We are investigating delays affecting CodeQL, the code analysis engine used by Code Scanning. Some users may experience delayed or incomplete code scanning results. Our engineering team is investigating. We will provide another update by 15:15 UTC.
Investigating
We have applied a mitigation to increase processing capacity. We are continuing to monitor to confirm full recovery. We will provide another update by 15:30 UTC.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Monitoring
CodeQL impact has been mitigated. We are continuing to monitor for durable recovery.
Resolved
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. <br /><br />We mitigated the impact by scaling our processing workers by 34%. Code Scanning results returned to normal processing times after the mitigation was applied. <br /><br />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.
Keep exploring
More from GitHub
Neighboring incidents on GitHub's timeline and the rest of their record on OutageDeck.