- GitHub reported recovery after reducing database-cluster load.
What changed
GitHub opened an incident at 09:16 UTC on September 13 covering degraded availability across several services. It subsequently reported replication delays in its collab database and increased authorization errors. Engineers reduced cluster load, reported recovery signs at 10:26 UTC and marked the incident resolved at 10:44 UTC.
Why it matters
For teams relying on GitHub to run delivery workflows, this provides a concrete incident window to compare with their own failed operations. The range of affected services also illustrates why separate workflow symptoms may warrant checking a shared provider incident.
What remains unproven
GitHub's explanation remains an incident update; the page promises a fuller root-cause analysis. It does not quantify affected customers, establish each customer's downtime or demonstrate that recurrence has been prevented.
Read beyond this page.
Recorded source-check date: 15 Sep 2026. A link is not, by itself, evidence that every claim has been independently verified.
Changes & version history
Version 3 · 15 Sep 2026
Scheduled release of checksum-bound AI-assisted editorial review
Version 2 · 15 Sep 2026
Checksum-bound editorial review scheduled for release
Version 1 · 15 Sep 2026
Source-linked private review edition