GitHub availability report: October 2026
GitHub's October 2026 availability report details significant Azure capacity expansion and targeted reliability improvements, but also acknowledges persistent write outages and a regional network disruption, highlighting ongoing operational challenges.
Intelligence analysis by Gemini 2.5 Flash

In October 2026, GitHub substantially increased its Azure Central US capacity and implemented several reliability fixes to reduce database load and improve incident handling. However, the month was marred by critical write outages and a regional network disruption, reinforcing the company's commitment to pairing capacity growth with enhanced operational safety and validated regional r…
Imagine GitHub is a huge playground where kids build amazing things with digital blocks. In October, they added lots of new swings and slides (more computer power) so more kids could play. But sometimes, the swings would get stuck, or a slide would suddenly close for a bit, making it hard for kids to build. So, even though they have more space, they're still working hard to make sure all the equipment works perfectly and safely, so no one's building gets interrupted.
Analysis
GitHub's October 2026 availability report provides a candid look into the platform's ongoing efforts to bolster its infrastructure while grappling with persistent reliability challenges. The company made significant strides in expanding its Azure footprint, particularly in Central US, where 140 of 151 production services and 32 of 50 MySQL primaries are now operational. This expansion included more than doubling compute capacity across nine Kubernetes clusters, a move that has already absorbed an 82% increase in migrated-service traffic since March, preventing the original datacenter from exceeding its prior operating range.
Azure Central US
The strategic shift towards Azure Central US represents a critical component of GitHub's long-term availability strategy. By migrating a substantial portion of its services and databases to this region, GitHub aims to enhance resilience and distribute its operational load. The report indicates that Azure is now serving a significant percentage of reads across migrated services (63%), monolith (66%), and Git (52%), demonstrating a tangible shift in traffic distribution. This capacity growth is not merely about scale but also about creating a more robust, geographically diversified infrastructure capable of handling increased demand and isolating potential failures.
Beyond raw capacity, GitHub also implemented targeted reliability improvements. These included increasing capacity for critical Azure control-plane requests, reducing NAT-gateway usage by 85%, and implementing connection limits to mitigate reconnect storms during dependency interruptions. A high-traffic GitHub Actions endpoint, handling over 250 million requests daily, was moved to a more efficient service path, drastically cutting peak database reads by 85%. Furthermore, requiring a minimum of three characters before searching repository topics reduced slow or terminated queries for that pattern by approximately 98%, showcasing a proactive approach to optimizing database performance and user experience.
October 7
Despite these advancements, October was not without its significant setbacks, underscoring the complexity of maintaining a global-scale service. The October 7 write outages, lasting nearly four hours, exposed a critical vulnerability stemming from an unsafe interaction between database orchestration and production routing. This incident led to GitHub Actions jobs staying queued or failing to start, impacting GitHub-hosted runners and causing delays in GitHub Pages updates and errors in various GitHub features. The root cause was identified as a partial networking failure between a datacenter region and cloud-hosted databases, which caused services to time out and restart, eventually overwhelming healthy regions due to insufficient capacity.
GitHub's response involved redeploying services, tracing failures to the networking issue, and failing over affected databases and storage to healthy regions. The company is now focused on making the job assignment service more resilient to sudden load increases, improving runner assignment prioritization, and enhancing detection and location of partial network failures. This incident, along with an October 29 Azure network disruption that affected over 34,000 signed-in users across three Central US availability zones, reinforced the report's central theme: capacity growth must be meticulously paired with safer operations, stronger isolation, and validated regional recovery mechanisms.
East US 3
The ongoing East US 3 buildout represents the next phase in GitHub's strategic infrastructure expansion, aiming to further diversify its operational footprint. Although currently about one week behind plan, this new region is slated to begin its first validated traffic ramp in the first week of December. This development is critical for enhancing GitHub's overall resilience, providing another geographically distinct environment to distribute services and mitigate the impact of regional failures.
The principle guiding this expansion remains consistent: 'availability, then capacity, then features.' This prioritization underscores GitHub's commitment to foundational stability before rolling out new functionalities. The continuous hardening of migration safety, dependency isolation, and regional recovery mechanisms in conjunction with the East US 3 buildout is essential to prevent future incidents from escalating and to ensure a more robust and reliable platform for its global user base.
Key points
- GitHub significantly expanded its Azure Central US capacity, migrating many production services and MySQL primaries.
- Compute capacity across nine Central US Kubernetes clusters more than doubled, absorbing substantial traffic growth.
- Targeted reliability improvements reduced database load and mitigated issues like NAT-gateway usage and reconnect storms.
- Critical write outages on October 7 and an Azure network disruption on October 29 exposed ongoing operational and isolation challenges.
- The company emphasizes pairing capacity growth with safer operations, stronger isolation, and validated regional recovery, with the East US 3 buildout progressing.
The substantial capacity additions in Azure Central US and the ongoing East US 3 buildout suggest GitHub is investing heavily in a more resilient, distributed infrastructure. These efforts, coupled with targeted reliability improvements, could lead to fewer and less impactful outages in the future, ensuring a more stable platform for developers worldwide.
Despite capacity growth, the recurring write outages and regional network disruptions in October highlight persistent challenges in operational safety and dependency isolation. Without fully validated regional recovery and stronger isolation, future incidents could still escalate, potentially impacting a large number of users and critical open-source projects.