GitHub’s Ignored Pause
GitHub’s 7 October 2026 write outages began with stale routes to retired database hosts. After recovery, a maintenance task bypassed a pause and restored the node’s leadership.
GitHub says it removed the node and automation now honours the pause. A Puppet update caused the regression. It reports no database data loss and successful post-recovery retries.
Further safeguards remain vendor-reported work, not independently verified repairs.
Check whether a maintenance pause blocks leadership changes, rather than merely stopping one job.
Sources
- GitHub combined report: 7 October, revised 12 October 2026.
- GitHub recurrence record: 7 October 2026.
