Enterprise
GitHub outage hits APIs, Copilot and Actions
GitHub’s August 17 outage disrupted APIs, Actions, Copilot and authentication, with web errors near 20% and downloads near 50%.
GitHub experienced a widespread outage on Monday, August 17, 2026, disrupting API requests, pull requests, webhooks, authentication, GitHub Actions and Copilot. Errors began at about 9:40 a.m. ET and continued intermittently until GitHub declared the incident resolved at 5:15 p.m. ET, according to Engadget.
James Harrison/Unsplash
At the peak of the incident, GitHub reported error rates of roughly 20% for web experiences and API traffic. Archive downloads and raw repository content downloads were failing at an estimated 50% rate.
The disruption also affected enterprise identity services, including SAML, OIDC, SCIM and Team Sync, as well as GitHub Actions, the platform’s automation service for testing and deployment. GitHub Copilot users experienced degraded availability, making the outage particularly disruptive for teams using AI-assisted coding workflows.
ITPro reported that Downdetector logged nearly 3,000 outage reports at one point. Its account says the incident was resolved at 9:15 p.m., later than Engadget’s 5:15 p.m. ET all-clear, while DevOps.com described recovery as beginning after engineers identified the faulty component and started corrective measures.
GitHub said at 1:34 p.m. ET that it had identified “the problematic component” and taken corrective action. Webhooks, API requests and pull requests returned to normal, but GitHub continued to report residual problems with its website, Copilot and authentication before the final resolution.
“We are experiencing high error rates around 20 percent for web experiences and API traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50 percent error rate.”
— GitHub status update
The company has not disclosed what caused the failure. GitHub promised to publish a detailed root cause analysis once its investigation is complete.
AI coding demand is straining GitHub
The outage comes as GitHub scales infrastructure to handle rapidly increasing activity tied to AI-driven software development. ITPro reported that GitHub initially planned a 10-fold capacity increase beginning in October 2025, then determined in February 2026 that it would need a 30-fold increase instead.
In an April 2026 blog post, CTO Vlad Fedorov said agentic workflows had “accelerated sharply.” He said repository creation, pull-request activity, API usage, automation and large-repository workloads were all growing quickly. GitHub’s stated priorities were availability first, capacity second and new features third.
“We are reducing unnecessary work, improving caching, isolating critical services, removing single points of failure, and moving performance-sensitive paths into systems designed for these workloads.”
— Vlad Fedorov, GitHub CTO
The company has also faced repeated reliability problems. ITPro reported eight additional outages in July 2026, including a prolonged GitHub Actions failure that GitHub called “unacceptable.” The company said it would accelerate the migration of GitHub Actions from its data centers to Azure, where it expects more headroom to absorb sudden demand spikes.
GitHub’s user count also varies by source: ITPro cites 225 million users, while DevOps.com puts the figure at roughly 180 million. APIContext chief product officer Jamie Beckland told ITPro that GitHub is on track for a 1,400% increase in commit volume from 2025 to 2026, with most of that growth coming from AI tooling.
The outage therefore affected more than a code-hosting website: it interrupted authentication, CI/CD pipelines and AI coding tools across development teams. The missing root-cause report will determine whether Monday’s failure was an isolated component problem or evidence that GitHub’s capacity work is still trailing demand.