Microsoft's GitHub Under Siege As SpaceX's Cursor Takes The AI Stack
Origin opened to paid Cursor users with day-one integrations as GitHub’s six-hour outage pushed error rates near 20% across core services, reports said.
- On August 17, GitHub experienced a 7-hour and 47-minute outage disrupting developers worldwide. CTO Vladimir Fedorov acknowledged the platform struggles to handle its current scale, writing, "If you were trying to ship software that day, we let you down."
- Microsoft-owned GitHub serves over 180 million developers globally yet recorded 257 incidents between May 2025 and April 2026. The company admits underlying infrastructure work has not kept pace with relentless traffic growth.
- Error rates climbed nearly 20% across pull requests and the API, with nearly 50% failure rates for archive and raw downloads. Microsoft Azure handles roughly 58% of GitHub's platform load, underscoring infrastructure dependency.
- On Monday, Cursor opened the beta of Origin, its own code hosting platform, to paid users. The timing coincided with GitHub's outage, though Cursor did not plan the launch date.
- Fedorov stated, "Our next milestone is an architecture that scales read capacity linearly with the number of readers." GitHub plans to accelerate cloud migrations and expand capacity to rebuild developer trust.
11 Articles
11 Articles
GitHub Apologizes for Major Outage and Performance Failures, Promises Fixes
GitHub has issued a public apology to its developer community after months of complaints about service degradation, slow performance, and unmet expectations around scaling. In a candid blog post, the Microsoft-owned platform acknowledged that it fell short of the reliability standards users have come to expect, promising concrete steps to expand capacity before frustration turns into widespread abandonment. The admission arrives at a moment when…
'We let you down': GitHub pledges to scale up before developers give up
GitHub's handwringing continued this week as CTO Vladimir Fedorov offered more detail about the August 17 outage – while carefully avoiding the word "sorry." The outage lasted 7 hours and 47 minutes and disrupted developers worldwide. Actions, pull requests, issues, Copilot, and APIs were among the services affected as the platform failed to scale with demand. "If you were trying to ship software that day, we let you down," wrote Fedorov. The in…
The platform revealed additional details about the massive outage on August 17, which lasted 7 hours and 47 minutes. The company admitted that it was unable to scale its critical infrastructure in time to accommodate the sudden increase in load.
The global failure of GitHub on August 17 revealed a capacity steering defect, aggravated during the resumption by the automatic referral of requests. The editor explains that he had yet added millions of processor cores and moved an increasing share of traffic to Azure. In an article on his website, GitHub [...] The post GitHub explains the breakdown of August 17 by a prolonged overload of Copilot appeared first on IT SOCIAL.
Coverage Details
Bias Distribution
- 75% of the sources are Center
Factuality
To view factuality data please Upgrade to Premium
