[2026-05-13] Incident Thread #195719
Replies: 6 comments 6 replies
-
UpdateWe 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. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe 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. |
Beta Was this translation helpful? Give feedback.
-
UpdateCodeQL impact has been mitigated. We are continuing to monitor for durable recovery. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.
-
|
There have benn TEN (https://www.githubstatus.com/history) incidents in 13 days. ZERO ROOT CAUSE ANALYSES HAVE BEEN PROVIDED. That's unacceptable. Don't commit to publishing root causes analyses in your status updates if they are never given. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
❗ An incident has been declared:
Incident with CodeQL
Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.
Beta Was this translation helpful? Give feedback.
All reactions