Cases › operational mistake › LR-2026-0604
GitHub outage caused by AI-driven traffic surge and configuration error
Preliminary Why: 1 report: 36Kr · subject to change · 1 independent report
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer, industry.
Severity major: test: many third parties, with a stated count of tens of millions of developers opening GitHub to the same failed page.
GitHub, a code hosting platform used heavily by developers and by AI agents, suffered a wide outage on February 9, 2026 (Beijing time). GitHub's incident report gave the root cause as an overload of the core database cluster responsible for authentication and user management. Press reports tie it to an engineering change made two days earlier that reduced a user settings cache refresh from 12 hours to 2 hours, compressing cache rewrites into a storm that spread through shared components to platform-wide connection exhaustion. GitHub's CTO named rapid load growth, tight coupling between services and a lack of protection against abnormal client traffic as structural causes. GitHub later announced plans to redesign its architecture, including better change management.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Primary63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
HarnessTool allow-list · Fail-closed defaults · Stop control
ApplicationHuman approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment
Infrastructure / targetEvidence
No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Show the full account: 1 items from the primary sources
What happened, in order
- 2026-03-18 Separate later incident: Webhook delay rose to 32 times the normal level.
Show every field, with its source and grade
What happened
Impact
Notes on gaps
The title's AI-driven framing is not directly supported for Feb 9 beyond that background. The Feb 2, Mar 5 and Mar 18 incidents are separate from this one and are listed only as context.
LR-2026-0604 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON