GitHub has published its account of this week's nearly eight-hour outage, tracing the developer pain to saturated load balancers, a faulty autoscaling policy, and a "latent retry bug in Visual Studio Code." According to GitHub, problems began at 1328 UTC on August 17 and weren't fully resolved until 2115 UTC – a 7-hour, 47-minute incident that produced elevated errors across Issues, Pull Requests, APIs, Actions, and Copilot. The immediate cause was network saturation on load balancers in the company's Central US facility, triggered when an Istio sidecar reached its concurrency limit. Surely autoscaling would add capacity as those limits were reached? Alas, no. A misconfigured policy monitored the host service but not the sidecar's concurrency limit, allowing a cascading failure to develop. "The problem," according to GitHub, "was worsened by optimistic retry logic which overloaded internal load balancers." Engineers mitigated the problem by temporarily reducing gateway retries through a code change and configuring the load balancers to reject inbound Copilot Token Service requests with HTTP 403 responses. Ah yes, Copilot. GitHub explained: "Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service." Most services recovered by 1636 UTC and Actions by 1803 UTC, but the Copilot Token Service took until 2102 UTC. "Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints," GitHub added. The Microsoft tentacle says it will correct the autoscaling policies, review retry limits, audit Istio concurrency settings, and address the VS Code behavior "that amplified Copilot token traffic." This latest incident could be the tipping point that sends some developers scurrying for an alternative. CloudBees CEO Moritz Plassnig noted in a LinkedIn post that "Cursor, OpenAI and several smaller startups are already building competitive solutions." "GitHub won't be the default solution going forward and we are looking at a much more bifurcated ecosystem (which is good and bad)." The findings will raise eyebrows among engineers. A misconfiguration and retry storm degraded a critical piece of infrastructure on which many organizations depend, leaving developers unable to work normally for hours. GitHub's reliability problems stretch back well beyond this week, as the company itself acknowledges. Developers have choices, and the pain/gain equation is not looking too favorable for the source shack. As Plassnig noted, alternatives keep cropping up – sometimes at the most awkward moment. As GitHub staggered, SpaceX-owned Cursor announced an early beta of Origin Code Hosting. ®