GitHub suffered a 7-hour, 47-minute outage on August 17 that disrupted github.com, authentication, GitHub Actions, APIs, pull requests, issues, and Copilot worldwide. GitHub said traffic had reached a new peak when a critical infrastructure component in its Central US data center failed to scale, creating capacity pressure that spread across its systems. Most services recovered that day after teams rerouted traffic and isolated affected infrastructure, while some Copilot services took longer because client-side retry loops increased traffic during recovery. The outage was GitHub’s second significant August incident, following an August 6 GitHub Actions failure. GitHub said neither event resulted from a code or configuration change; both were capacity failures. Monthly commits grew from 1.4 billion in April to 2.9 billion, increasing system demand. Since April, GitHub has added more than 3 million CPU cores, 120 petabytes of high-speed storage, and additional network capacity, while accelerating its migration to Azure. Azure now handles about 58% of GitHub platform load and half of Git operations, up from 12% of platform load in May. GitHub plans to limit retries and apply retry budgets and variable timeouts between services, review lower-priority CPU and memory alerts, isolate critical systems, and remove shared dependencies. It is also developing an architecture intended to scale read capacity linearly for large monorepos.

GitHub.com is experiencing degraded performance, particularly in Git Operations. A problematic component has been identified and corrective actions are underway, but residual impacts are affecting multiple services.

Multiple GitHub services are experiencing issues, causing workflow runs to fail or be delayed, and some queued jobs may time out. Engineers are implementing mitigations and rolling out a fix across all affected systems.

GitHub is restructuring its bug bounty program to enhance collaboration with the security research community and improve overall platform safety. Changes to the program aim to better recognize and reward researchers for identifying and reporting vulnerabilities.

A large-scale malware distribution campaign on GitHub has been identified, involving 10,000 repositories that distribute Trojan malware. These repositories originate from different contributors and share a common pattern, enabling the creation of a script to find them.

Microsoft is adding Amazon Web Services capacity to GitHub to manage increased coding activity driven by AI advancements. This decision deviates from the original strategy of fully integrating GitHub's infrastructure with Microsoft's Azure cloud.

Microsoft's GitHub has banned security researcher Nightmare-Eclipse after they posted zero-day Windows exploits. The researcher claims this action has ruined their life and has promised further retaliation against the company.

GitHub plans to increase its capacity by 10X starting in October 2025 to enhance reliability and failover capabilities. Recent incidents have prompted the company to take action to improve service availability.

An incident affecting multiple GitHub services has been resolved, with webhooks now operating normally. The degradation impacting Actions and Copilot has been mitigated, and monitoring is ongoing to ensure stability.

FAKKU, LLC has issued a DMCA takedown notice regarding gallery-dl and 28 other repositories, requesting the removal of certain files. The recipient is considering switching platforms rather than rewriting the entire repository history to comply with the notice.