What’s gone wrong at GitHub?

Estimated reading time: 8 minutes

Key takeaways:

• GitHub’s uptime has plummeted.
• Rapidly scaling agentic AI workflows have overwhelmed the platform.
• Focused on recovery, GitHub’s leadership has shifted from growth at all costs to an availability first mandate, but patience is running out.

For most of its life, GitHub has been remarkably reliable.  Then, somewhere in the last year or so, that stopped being the case. What happened?

In 2024, GitHub logged 119 service incidents, including 26 major ones. The average resolution time was around 106 minutes. Frustrating, but manageable. 

Then, between May 2025 and April 2026, incident monitoring service IncidentHub tracked 257 separate incidents on GitHub, of which 48 were classified as major outages.

Join LeadDev.com for free to access this content