🔧 GitHub Availability Update
• Two recent incidents (merge queue bug & Elasticsearch outage) deemed unacceptable; GitHub apologizes.
• Original 10X capacity plan (Oct 2025) upgraded to 30X by Feb 2026 due to rapid agentic development growth.
• Exponential growth in repos, PRs, API usage, monorepos stresses multiple systems simultaneously.
🚨 Recent Incidents
• April 23 – Merge Queue Bug: Squash merges with multiple PRs in a group produced incorrect commits. Affected 230 repos, 2,092 PRs. No data loss; manual repair needed for some branches.
• April 27 – Elasticsearch Outage: Cluster overloaded (likely botnet attack) stopped returning search results. No data loss, but parts of UI broken. Root cause analysis pending.
🔜 Actions Taken & Planned
• Short-term: fixed webhooks backend, session cache, auth flows; added compute via Azure migration.
• Isolating critical services (git, Actions) to reduce blast radius; moving code from Ruby monolith to Go.
• Long-term: pursuing multi-cloud resilience; investing in monorepo performance & merge queue optimization.
📢 Transparency Commitment
• Updated status page with availability numbers; statusing all incidents, large and small.
• Improving incident categorization and customer reporting channels.
We read every email, social post, support ticket, and we take it all to heart. We’re sorry.
citeVlad Fedorov, GitHub/cite
🔗 github.blog
⏱️ 2m 51s saved