An update on GitHub availability

· databases devtools ai-agents · Source ↗

TLDR

  • GitHub’s CTO details two recent incidents and a scaling overhaul driven by agentic development workflows accelerating sharply since late 2025.

Key Facts

  • GitHub expanded its capacity plan from 10X (October 2025) to 30X by February 2026, driven by agentic workflow growth.
  • An April 23 merge queue bug caused incorrect squash merges in 230 repositories affecting 2,092 pull requests; no data was lost.
  • An April 27 Elasticsearch overload (likely a botnet attack) disrupted search-backed UI across pull requests, issues, and projects; Git and APIs were unaffected.
  • GitHub is isolating critical services, migrating performance-sensitive code from Ruby to Go, and moving toward multi-cloud infrastructure.

Why It Matters

  • Both incidents exposed single points of failure that GitHub acknowledges it had not yet isolated before they were hit.
  • GitHub committed to statusing all incidents and publishing root cause analyses to improve transparency with customers.

Vladimir Fedorov, The GitHub Blog · 2026-04-28 · Read the original

Related coverage