A GitHub outage thread produced the first cited number on agent-driven commit volume

The thread asks GitHub employees to explain the platform's recent reliability record. No employee answered on the record. What it produced instead was a set of figures attributed to GitHub COO Kyle Daigle: that AI-assisted coding has raised commit volume 14 times in the past year, that there were 1 billion commits in 2025 and 275 million per week as of roughly three months ago, and that 20% of all GitHub accounts were created in the past six months. Those figures reach the thread through links to Daigle's posts on X, which this edition has not opened; they are reported here as claims by a named GitHub executive, not as verified platform statistics. The thread's most substantive disagreement is whether volume explains anything: commenter maccard notes GitHub's reliability problems predate the agentic-coding surge, and jjice points at a community-maintained uptime history showing degradation beginning around 2020. Several commenters attribute the problems to the ongoing migration to Azure instead. One first-hand report is worth its own line: evanelias, who operates a GitHub app, describes a bot adding the app to 1,700 repositories overnight and then "rapid-firing commits which each affected hundreds of files."

Why it matters: The supply side and the demand side are describing the same phenomenon in the same week. Cursor's engineering post says agents create vast numbers of throwaway repositories and that hosting built for the old population cannot serve them economically; this thread says a platform serving the old population is visibly struggling and cites a 14x commit figure to explain it. If your factory's CI or release path depends on a single hosted forge, that dependency is now carrying load it was not sized for, and the vendor telling you so most clearly is the one selling the alternative.