GitHub experienced a major outage on August 17, 2026. GitHub's CTO, Vlad Fedorov, wrote that 'On August 17, GitHub experienced an outage that lasted 7 hours and 47 minutes,' which 'disrupted github.com, authentication, GitHub Actions, APIs, pull requests, issues, and Copilot, affecting developers and organizations around the world.' He called it GitHub's 'second significant incident in August, following an actions failure on August 6,' and said the root cause in both cases was a failure to scale infrastructure fast enough, not a code or configuration change.[4]
GitHub's usage has grown sharply through 2026. Fedorov's post said, 'Since April, monthly commits have grown from 1.4 billion to 2.9 billion,' which he said explains the capacity pressure behind the August outages, 'but it does not excuse these outages.' GitHub said it responded by adding 'more than 3 million CPU cores, 120 petabytes of high-speed storage, and significant network capacity' to its data centers while speeding up its migration to Azure.[4]
GitHub moved all Copilot plans to usage-based billing on June 1, 2026. GitHub's company-news blog announced the change in a post that said, 'all GitHub Copilot plans will transition to usage-based billing on June 1, 2026,' replacing the prior system of counted 'premium requests' with a model based on token consumption, because, GitHub wrote, 'the current premium request model is no longer sustainable.'[2]