At 9:40 AM (Eastern Time), error messages began popping up across GitHub's various services. For many developers who rely on the platform to push code and review pull requests, this Monday was off to a rough start right from the get-go.
According to updates on GitHub's official status page, the issues spanned API requests, pull requests, and webhooks — and even Copilot, which has been heavily used for AI-assisted coding lately, didn't escape unscathed. Around 11 AM, an official update stated: "We are experiencing an elevated error rate of about 20% for our web experience and API traffic, and around 50% for archive and raw repository content downloads." The team said it was working on mitigation based on the findings of its investigation.
At 1:34 PM, GitHub announced it had pinpointed the "problematic component" and was implementing "corrective measures," with webhooks, API requests, and pull requests gradually coming back online. But the saga wasn't over yet — as of 3:05 PM, Copilot and the GitHub website itself were still acting up. The real "all clear" message didn't come until 5:15 PM. All told, the outage spanned nearly eight hours.
The exact cause of the outage has not yet been made public, with GitHub saying it will provide a "detailed root cause analysis" once its investigation is complete. Notably, this marks the second major outage for a Microsoft-owned platform in just a few weeks, following a multi-hour disruption to several Xbox services earlier last month.
This article is based on reporting from Engadget.
