@GergelyOrosz: Incredible how GitHub’s eng team knows reliability (having zero nines) is their #1 problem for ~6 months now and seemin…
Summary
The tweet highlights GitHub's ongoing reliability problems, criticizing the engineering team for not resolving frequent outages despite having skilled engineers, and suggests past architectural decisions are to blame.
View Cached Full Text
Cached at: 08/17/26, 08:19 PM
Incredible how GitHub’s eng team knows reliability (having zero nines) is their #1 problem for ~6 months now and seemingly not being able to get a handle on it. Despite so many solid engineers working on it
My bet: arch decisions years ago bite back v hard now
Mehul Mohan (@mehulmpt): it is borderline insane that this platform is down almost every other week.
Similar Articles
github and the crime against software
This article criticizes GitHub for frequent outages, poor reliability, and prioritizing AI features over fundamental infrastructure, arguing it reflects broader decay in big tech software services.
GitHub is sinking
The article argues that GitHub's reliability and culture have significantly declined since Microsoft's acquisition, citing uptime issues and 'slop' as reasons for developers to migrate to alternatives.
The August 17 outage, and the work ahead
GitHub experienced a significant outage on August 17 due to capacity failures, disrupting services for hours. The company is accelerating efforts to improve infrastructure reliability and scale systems to handle growth.
GitHub's plan for Agents (90 minute read)
The article examines how the explosive growth of AI coding agents (1400% in 2026) is straining GitHub's infrastructure, leading to notable uptime issues, and discusses GitHub's plans to adapt its platform for this new era.
The amount of activity on GitHub right now is crazy. Thoughts?
GitHub experienced a significant outage on August 17, and the company has published a blog post discussing the incident and outlining the work ahead to prevent future issues.