← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

GitHub October 2026 Availability Report Details Azure Migration Progress and Outages

🔄 Updated 8d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • 140 of 151 production services migrated to Azure Central US.
  • Azure Central US compute capacity more than doubled.
  • Experienced write outages and an Azure network disruption.
  • East US 3 buildout is slightly behind schedule.

Azure Migration and Capacity Expansion

GitHub continued its migration to Azure, with 140 of 151 production services and 32 of 50 MySQL primaries now operating in Azure Central US as of November 9. Azure handled 63% of migrated-service reads, 66% of monolith reads, and 52% of Git reads. A compute expansion across all nine Central US Kubernetes clusters more than doubled capacity, supporting an 82% increase in migrated-service traffic since March.

Targeted Reliability Improvements

Several specific reliability improvements were implemented. Actions changes increased capacity for critical Azure control-plane requests. A NAT-gateway mitigation reduced usage by 85%, preventing approximately 800 expected job failures. Connection limits and client improvements were also introduced to mitigate reconnect storms following dependency interruptions.

Database Load Reduction

GitHub addressed concentrated sources of database load. A high-traffic GitHub Actions endpoint, processing over 250 million requests daily, was moved to a more efficient service path, resulting in an 85% reduction in peak database reads. Additionally, requiring at least three characters for repository topic searches reduced slow or terminated queries for that pattern by approximately 98%.

October Incidents and Challenges

Despite progress, October saw reliability issues. Write outages on October 7 exposed an interaction between database orchestration and production routing. An Azure network disruption on October 29 affected all three Central US availability zones and at least 34,128 signed-in users. These incidents underscore the need for safer operations and stronger isolation.

Future Plans

The buildout of East US 3 is approximately one week behind schedule. The next phase, involving its first validated traffic ramp, is planned for the first week of December. GitHub continues to focus on hardening migration safety, dependency isolation, and regional recovery capabilities.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

GitHub's October 2026 availability report indicates substantial progress in migrating services to Azure Central US, with 140 of 151 production services and 32 of 50 MySQL primaries now running there. Despite increased capacity and targeted reliability improvements, the month saw write outages and an Azure network disruption, highlighting ongoing challenges with operational safety and regional recovery.