Microsoft’s GitHub Hit by Major Outage as AI-Driven Demand Strains Infrastructure
GitHub, the Microsoft Corp.-owned code hosting platform serving more than 180 million developers, is still reeling from a widespread outage on Monday that severely disrupted software development pipelines globally. The hours-long incident was the latest in a relentless series of reliability failures for a service struggling to keep pace with an unprecedented surge in artificial […]
Microsoft's GitHub, the world's largest code hosting platform used by over 180 million developers, suffered a major outage on Monday that severely disrupted software development pipelines worldwide. The incident, which lasted for several hours, was the latest in a string of reliability issues for a service struggling to handle a surge in artificial intelligence-assisted coding traffic.
The problems began around 9:40 a.m. EDT, with initial reports of performance degradation across core services. The issue quickly escalated, with error rates surpassing 20% for web interface and API traffic, while download rates for archive and raw repository content dropped by half. Critical features such as GitHub Actions automated testing, webhooks, GitHub Pages, and the AI pair-programmer Copilot were significantly impacted.
Web monitoring service Downdetector recorded thousands of user reports during the peak of the disruption, and the outage coincided with minor interruptions in Microsoft Teams. GitHub engineers identified the problematic component midday and deployed corrective measures, but the root cause of the outage remained undisclosed. This service interruption comes amid mounting developer frustration over GitHub's operational stability, with the platform experiencing eight separate degradation incidents in July alone.
Earlier this year, GitHub acknowledged that AI-assisted workflows were placing significant strain on backend infrastructure, and the company had set an ambitious goal to expand platform capacity thirtyfold to accommodate the growing traffic. The frequent downtime is prompting engineering organizations to reassess their reliance on single-provider ecosystems, as an infrastructure outage now effectively halts the modern software assembly line.
For technical leaders, these recurring disruptions are transforming redundancy from a secondary consideration to an operational imperative.
Written by urgent.news from DevOps.com's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.