A major technical outage struck GitHub on Monday morning, disrupting workflows for millions of developers worldwide for several hours as critical services, automated testing pipelines, and artificial intelligence (AI) coding tools suffered high error rates.
The hosting platform — a subsidiary of Microsoft Corp. that supports roughly 180 million users — first reported performance issues around 9:40 a.m. EDT. The disruption quickly escalated as thousands of users flooded outage-tracking platforms like Downdetector to report failing repositories, broken downloads, and degraded performance.
At the peak of the incident, GitHub confirmed error rates of approximately 20% across its web interface and API traffic. Core functions faced even steeper degradation: raw repository content and archive downloads suffered error rates near 50%, while enterprise authentication features like SAML, OIDC, SCIM, and Team Sync were broadly impacted.
The chaos broadened by mid-morning when GitHub confirmed degraded availability for GitHub Copilot, its AI-powered coding assistant, as well as GitHub Actions, which automates software deployment and testing. Minor outages were also reported across related Microsoft services, including Microsoft Teams.
The outage landed at a particularly disruptive moment. Monday morning is typically when engineering teams kick off weekly sprints and clear code backlogs. Stalled pipelines and authentication failures left developers staring at server errors, sparking widespread frustration on social media and service monitoring forums. Some users noted that minor performance hitches had become an increasingly frequent occurrence in recent weeks.
By 12:36 p.m. EDT, GitHub updated its official status page to confirm that engineers had identified the faulty component and initiated corrective measures. The platform reported “strong signs of recovery,” though error rates remained slightly elevated as services were restored.
While GitHub has not yet disclosed the exact root cause of the breakdown, the incident highlights the platform’s exponential growth.
Spurred by an industry-wide push toward AI-driven software development, GitHub executives noted earlier this year that the company had to rapidly scale its capacity infrastructure to keep pace with record-high traffic.
A full post-incident review is expected once service completely stabilizes across all regions.
