Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-05 · source-backed
Mitchell Hashimoto co-founded HashiCorp. Maintained Ghostty on GitHub for 18 years. Last week he pulled his project off the platform and said it's "no longer a place for serious work."
That's not a random internet complaint. That's one of infrastructure's most respected builders walking away publicly.
Fireship's video hit 907K views documenting the crisis: 257 tracked incidents from May 2025 to April 2026, with February 2026 the worst month at 37. A merge-queue regression silently reverted commits across 658 repositories. The May 4 outage degraded Issues, Webhooks, and Codespaces. GitHub CTO Vlad Fedorov attributed instability to "architectural coupling allowing localized issues to cascade across critical services" and admitted they can't adequately shed load from misbehaving clients.
IncidentHub's analysis paints an even starker picture. This isn't a blip. It's a trend with no reversal signal.
For builders, the calculus has changed. If your CI/CD pipelines depend on GitHub Actions, your webhook-triggered deployments depend on GitHub's event system, and your coding agents depend on GitHub's API being responsive. Every one of those is now a single point of failure with a documented 70% monthly incident rate.
I don't think you need to leave GitHub. But you need fallback strategies. Cache your dependencies outside GitHub. Have a secondary CI trigger mechanism. If you're running agent workflows that poll GitHub APIs, build in graceful degradation. And if you're building anything where silent commit reversion could be catastrophic, you need an independent verification layer.
The uncomfortable question nobody's asking: is GitHub's reliability crisis related to the massive compute they're dedicating to Copilot infrastructure? When you add AI inference at scale to a platform that was already struggling with growth, something gives.
Each link below shares sources, entities, or timing with this story.
Mitchell Hashimoto works at HashiCorp / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Mitchell Hashimoto works at HashiCorp); both cover Copilot, GitHub, GitHub Actions, HashiCorp; overlapping topics (action, hashimoto, platform).
Microsoft released Copilot / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Microsoft released Copilot); both cover Codespaces, GitHub, GitHub Actions; overlapping topics (action, admitted, agent, commit, month).
Linked by a graph relationship (Microsoft released Copilot); both cover Copilot, GitHub, GitHub Actions; overlapping topics (action, incident).
Copilot uses Claude / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Copilot uses Claude); both cover Copilot, GitHub, When; overlapping topics (action, agent).
Claude Code uses GitHub Actions / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses GitHub Actions); both cover April, Copilot, GitHub; overlapping topics (already, month).
Microsoft released Copilot / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover April, Copilot, GitHub; overlapping topics (agent, month).
Microsoft released Copilot / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover Fireship, GitHub, GitHub Actions; reported by the same outlet (youtube.com).
Copilot uses Claude / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Copilot uses Claude); both cover April, February, When; overlapping topics (infrastructure, month).