Is GitHub Down?

May 13 , 16:03 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. May 13 , 15:30 UTC Update - CodeQL impact has been mitigated. We are continuing to monitor for durable recovery. May 13 , 15:26 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. May 13 , 14:58 UTC Update - 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. May 13 , 14:43 UTC Update - 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. May 13 , 14:41 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

May 6 , 19:04 UTC Resolved - On May 6, 2026 between 15:12 and 19:02 UTC creation of new pull request review threads on GitHub.com failed. This included new line comments and file comments on pull requests. Existing PRs and previously created comments were unaffected. This incident was caused by a 32-bit integer key reaching its maximum value in a Vitess lookup table used during PR thread creation. The primary table had been migrated to a 64-bit integer key but the Vitesse lookup table remained 32-bit. Once the values in the primary table passed the available 32-bit ID space in the lookup table, attempts to create new review threads began failing, resulting in near 100% failure rate for new thread creation requests. We mitigated the issue by updating the impacted lookup table definitions across all shards to use 64-bit integer column types, increasing the available ID range and restoring normal operation. Service was fully restored once the schema changes competed globally. To help prevent similar incidents, we are expanding existing monitoring of database columns to include Vitess lookup tables to notify in advance of any tables that is approaching a column size limit. This work is intended to provide earlier detection of columns approaching size limits before customer impact occurs. May 6 , 19:04 UTC Update - Mitigations have been fully applied and we are seeing full recovery of functionality on Pull Request threads. We are continuing to monitor to ensure sustained recovery. May 6 , 17:52 UTC Update - Creation of new Pull Request threads (including line and file comments) continues to be affected although we are seeing partial recovery. A mitigation is being applied to continue to accelerate recovery with complete recovery expected by 8:00pm UTC. Top-level comments on pull requests still function and should remain usable during recovery. Opening and merging pull requests, actions, and other pull request operations remain functional. May 6 , 16:20 UTC Update - Creat

May 5 , 18:35 UTC Resolved - Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones, were not affected. The impact was caused by reduced SSH capacity at one of our data center sites. During a period of high traffic, the remaining hosts became overloaded, leading to connection exhaustion and some failures for SSH-based operations. Additional capacity was provisioned to expand SSH capacity and resolve the incident. The expanded capacity was fully online by 18:18 UTC. To reduce the likelihood of similar incidents, we will implement faster scaling solutions for SSH infrastructure and improved alerting for host availability and capacity thresholds. May 5 , 18:35 UTC Update - We've completed our mitigation to prevent further impact. At this time the incident is considered resolved. May 5 , 18:25 UTC Monitoring - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability. May 5 , 17:26 UTC Update - We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place. May 5 , 17:23 UTC Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate. May 5 , 16:54 UTC Monitoring - Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact. May 5 , 16:49 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.