TLDR Tech / Data
Saturation at GitHub: the saga continues
A GitHub outage was triggered when a background cleanup job saturated a shared database primary, while monitoring incorrectly showed the cluster as healthy because it only watched replica lag. Long request timeouts and repeated retries then amplified the failure, highlighting how partial health signals and retry storms can turn database saturation into a site-wide incident.
Read the full story