4 dominant themes in the discussion
| Theme | Illustrative quote |
|---|---|
| Weekend stability – many users point out that GitHub experiences far fewer outages on weekends, suggesting problems are load‑driven during busy weekdays. | “Weekends are the untapped frontier. Still room to scale.” – sd9 |
| Deployment density & AI‑driven load – the constant stream of merges, deployments, and AI‑generated code is identified as a major stressor on the platform. | “At least as of when I left the company, GitHub was being deployed to fairly close to once every 60‑90 minutes … there aren’t dedicated releases … more outages when you try to fix those issues without fully considering the scope.” – rufo |
| Management focus on AI over core reliability – commenters argue that Microsoft‑driven priorities (e.g., “USE MOAR AI”) are diverting resources from the essential service stability. | “They’re making political decisions based on what they sell vs what’s actually useful for their use case.” – prepend |
| Desire for self‑hosted or alternative solutions – frustration leads some to self‑host GitHub or migrate to other services, viewing GitHub’s uptime as a risk. | “All these companies brag about being hyperscalers and cannot scale github.” – faangguyindia |
These four themes capture the most‑repeated observations andarguments across the thread.