Do Son 
This week, Microsoft’s code hosting platform, GitHub, experienced a prolonged and widespread outage. This disruption significantly impacted countless developers and users who rely heavily on the service. Yesterday, GitHub published an incident review report. The document indicates that a massive surge in usage primarily caused internal infrastructure errors. Furthermore, other structural inefficiencies magnified the severity of this outage.
Now, GitHub Chief Technology Officer Vladimir Fedorov has released a blog post to address the situation directly. He explicitly emphasized that neither code nor configuration changes triggered this failure. Instead, compounding issues stemming purely from overwhelming traffic caused the collapse. In short, the platform struggled immensely, and leadership felt compelled to explain the reality.
Monthly Commits Skyrocket to 2.9 Billion
Within his blog post, Fedorov shared staggering growth statistics regarding pull requests, code commits, and new repository creations since 2023. The data reveals that between 2023 and 2024, GitHub processed only about 50 million code commits monthly. By early 2025, this figure grew modestly to roughly 70 million.
However, beginning in late 2025, the volume of monthly code commits escalated at a truly terrifying velocity. By August 2026, this number had skyrocketed to an astonishing 2.9 billion. Naturally, pull requests and new repository creations also shattered previous records. Consequently, the platform simply buckled under the immense pressure.
Fedorov stressed that code or configuration alterations did not cause the two recent outages. A profound lack of capacity served as the fundamental root cause for both events. GitHub failed to scale its critical components rapidly enough, resulting in demand vastly exceeding available resources. While the company offers no excuses, they are aggressively accelerating migration and expansion efforts. For deeper insights, read about the August 17 outage and the work ahead directly from the source.
Adding 3 Million CPU Cores
To combat these severe traffic surges, the organization is expediting its migration toward Microsoft Azure. Currently, Azure handles approximately 58 percent of platform workloads and 50 percent of all Git operations. This represents a massive increase from a mere 12 percent back in May.
Simultaneously, the company is frantically deploying additional processing power and storage capacity. This year alone, GitHub integrated 3 million new CPU cores alongside 120 petabytes of high-speed storage. Only through this colossal scale of expansion can the platform maintain stability for the majority of the time.
Reallocating Human Resources
An intriguing spectacle of the artificial intelligence era is the shifting of corporate priorities. GitHub must now reallocate significantly more human resources toward ensuring basic system availability. Historically, managing uptime did not require an exceptionally large dedicated team. Yet, in the current landscape, platform stability has transformed into a paramount challenge. Therefore, leadership had no choice but to redirect numerous teams and vast resources toward fortifying reliability.
This dedicated unit will dramatically intensify testing protocols and enhance secure deployment capabilities. Furthermore, they will introduce superior observability mechanisms and construct highly effective alerting systems. Ultimately, they aim to elevate the overall reliability of the platform from every conceivable angle. Fedorov noted that the team has already achieved notable progress in this domain. However, the mission remains incomplete, so they require additional time to perfect these vital improvements.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.
Buy Me a Coffee
PayPal
