GitHub’s 7‑hour outage exposed capacity limits in its Central US data center, prompting a multi‑million‑core expansion and a shift to Azure for resilience.

GitHub’s seven‑hour outage on August 17 revealed critical capacity constraints in its Central US data center, spurring a multi‑million‑core hardware expansion and a strategic shift toward Microsoft Azure for added resilience.

What happened on August 17

The incident began around 02:00 UTC when a power‑distribution failure triggered a cascade of server shutdowns. Engineers worked to restore services, but the outage persisted for roughly seven hours, affecting GitHub.com, GitHub Enterprise Cloud, and related APIs.

Post‑mortem analysis identified that the data center had been operating near its maximum compute capacity, leaving little headroom for unexpected spikes or hardware faults.

Immediate response and remediation

GitHub’s site‑reliability team deployed additional compute nodes from a nearby overflow pool, but the limited inventory could not fully compensate for the loss. The team also rerouted traffic to secondary regions where possible, though latency increased for many users.

To prevent recurrence, GitHub announced a plan to add several million CPU cores to the Central US facility over the next twelve months, expanding both the physical rack space and the power budget.

Long‑term strategy: Azure partnership

Beyond hardware upgrades, GitHub is deepening its partnership with Microsoft Azure. The cloud provider will host a new replica of critical services, offering geographic redundancy and diversified power sources.

This move aligns with GitHub’s broader resilience roadmap, which aims to distribute workloads across multiple cloud and on‑premise environments to mitigate single‑point failures.

  • Expand compute capacity in Central US data center
  • Deploy Azure‑based replica for critical services
  • Implement automated failover between regions
  • Increase monitoring of power and cooling systems
Our goal is to ensure that a single hardware incident never again disrupts the global developer community.

The outage underscored the importance of capacity planning for platforms that serve billions of requests daily. GitHub’s combined hardware expansion and Azure integration represent a proactive approach to safeguarding developer workflows.

For the full post‑mortem and roadmap details, see GitHub Blog coverage of the August 17 outage.