The Pulse: AI load breaks GitHub – why not other vendors?
Summary
GitHub's reliability has significantly degraded, with third-party measurements indicating a drop to 86% availability this month, down from 90% last month. This decline has led prominent open-source contributor Mitchell Hashimoto to express concerns about GitHub's suitability for professional work. GitHub leadership attributes the service degradation to a 3.5x increase in load, potentially linked to AI-driven activity. Concurrently, Anthropic faces criticism for silently nerfing Claude Code, banning companies from its Claude service, and implementing baffling price increases, suggesting a shift towards an "extraction" revenue model. The broader industry pulse includes dramatic price increases for GitHub Copilot, explosive growth for Codex, Google's efforts in coding models, and potential acquisition talks for Cursor by SpaceX.
Key takeaway
For CTOs and VPs of Engineering evaluating developer platform stability, GitHub's recent reliability issues and Anthropic's service changes highlight the critical need for vendor due diligence. You should diversify critical tooling or implement robust fallback strategies to mitigate risks from single-vendor dependencies and unexpected service degradations or policy shifts.
Key insights
Increased AI-driven load is impacting core developer infrastructure reliability and business models.
Principles
- Reliability is paramount for professional platforms.
- Open source "building blocks" drive adoption.
In practice
- Monitor third-party reliability metrics.
- Evaluate vendor service changes carefully.
Topics
- GitHub Reliability
- AI Service Load
- Anthropic Business Practices
- Open-Source Economy
- GitHub Copilot
Best for: CTO, VP of Engineering/Data, Entrepreneur, Director of AI/ML, AI Product Manager, Software Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by The Pragmatic Engineer.