GitHub: Stale routing records send database writes to retired servers, twice in one day
On October 7, 2026, GitHub had two write outages, the first lasting about 10 minutes and the second about 9 minutes, caused by the same fault, which GitHub attributes to an unsafe interaction between its database orchestration and production routing. During routine maintenance, a new machine that manages database write routing started with outdated records that still listed retired database servers. When it was automatically elected leader, it published routing settings that sent writes for several core databases to those retired servers, and the settings passed existing validation. Pushes, sign-ins, pull request and issue updates and application programming interface (API) writes were disrupted, and web and API request failures peaked at 8.9% in the first outage, affecting more than 12,000 organizations, and at 9.3% in the second, affecting more than 11,000.
GitHub