GitHub Service Disruption on February 10, 2026: Database Memory Pressure Caused Intermittent Errors
By
gpi
3mo ago· 3 min readenNews
65/100
Toasty
Bagelometer↗
A weekday bagel. Dependable, satisfying, no fuss.
Score65TypenewsSentimentneutral
Summary
GitHub experienced a service disruption on February 10th, 2026, between 14:35 UTC and 15:58 UTC, affecting web experiences including Pull Requests and Authentication. The incident resulted in intermittent 5xx errors and timeouts, with web traffic error rates peaking at approximately 2%. The root cause was increased load on a critical database causing significant memory pressure. GitHub resolved the issue by applying a configuration change to increase available memory on the database host.
Key quotes
· 4 pulledOn February 10th, 2026, between 14:35 UTC and 15:58 UTC web experiences on GitHub.com were degraded including Pull Requests and Authentication, resulting in intermittent 5xx errors and timeouts.
The error rate on web traffic peaked at approximately 2%.
This was due to increased load on a critical database, which caused significant memory pressure resulting in intermittent errors.
We mitigated the incident by applying a configuration change to the database to increase available memory on the host.
GitHub's Status Page - Disruption with some GitHub services.
