Microsoft's GitHub Under Siege As SpaceX's Cursor Takes The AI Stack

dev.by

Factuality

Ownership

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.

itsocial.fr

Factuality

Ownership

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.

Numerama

Factuality

Ownership

GitHub went back to the causes of the giant crash that paralyzed the platform on August 17th. The reason: a peak of traffic that the infrastructure could not absorb."If you had planned to deploy software that day, we are sorry for this inconvenience."On August 20th, 2026, GitHub apologized to GitHub.

GIGAZINE

Factuality

Ownership

A global outage occurred at GitHub from August 17th to 18th, 2026, making many services, including GitHub.com, GitHub Actions, and GitHub Copilot, difficult to use. GitHub published its investigation results on August 20th, explaining that critical infrastructure in its data centers in central the United States was unable to scale its processing capacity in response to record-high traffic, leading to a chain reaction of outages. Read more...