GitHub's Azure move: 120 of 160 services by October 7

GitHub's availability report, published October 14, 2026, covers August and September together. As of October 7, 120 of 160 production services ran in Central US, and 13 of 51 primary MySQL databases had moved. Azure also carried 65.4% of read traffic for GitHub's core application, 48.3% of Git read traffic and 80.2% of stream-processing traffic. GitHub notes those percentages cover different workloads and should not be added together.

GitHub paused Central US deployments and traffic increases on September 11. Capacity was uneven across availability zones. Permanent ramps resumed September 18 after temporary relief, and GitHub aims to unlock all available capacity by the end of October. The September 30 goal to deploy every production service there was missed. During a planned database failover, an automated emergency process disconnected Central US database copies and disrupted customers in that region. GitHub disabled that process during planned handoffs while improving recovery.

Outside the migration, 24 authentication-core tables moved off GitHub's oldest shared database. That removed roughly one million queries per second from its replicas. The cluster behind issues and pull requests dropped about 980 million unnecessary edit-history rows, freeing an estimated 1.8 terabytes. Weekly deadlocks fell about 77% from their June peak. For Actions, production changes cut measured Redis operations by about 28% and relative CPU by about 30%.

A separate infrastructure cache reduced Redis bandwidth by 84%. GitHub lists the August 6 Actions outage, the August 17 github.com outage, the September failover disruption and the capacity pause as reminders that measured gains matter only when they cut customer risk in real conditions.