1. GitHub’s reliability is slipping
The thread is dominated by reports of frequent 500‑level errors, degraded “Git Operations” and “Copilot & Actions” services.
“I’m getting 500 errors intermittently on fetch and checkout operations in my CI pretty consistently at the moment.” – alemanek
“GitHub has been shit lately. What the fuck is going on?” – khaledh
“The only thing that can kill e.g. github is if they move fast and break things like they do recently.” – risyachka
2. The need for a fallback or self‑hosted alternative
Because GitHub is a single point of failure, many users point to self‑hosting or open‑source alternatives (Codeberg, Forgejo, Gitea).
“A bare repo over SSH is the simplest way to keep control and reduce attack surface.” – hrmtst93837
“If you’re using GitHub professionally and pay for GitHub Actions… you can switch to a VPS and self‑host Gitea/Forgejo in less time.” – Imustaskforhelp
“Codeberg might be a little slower on git cli, but at least it's not becoming a weekly ‘URL returned error: 500’ situation.” – joecool1029
3. Workflows and AI workloads are being hit hard
The outages are not just a nuisance; they break CI pipelines, package registries, and the new AI‑driven workflows that rely on GitHub.
“When GitHub degrades, the blast radius is surprisingly large because it breaks entire build and release chains, not just repo browsing.” – pothamk
“I hit rate limits checking on CI jobs (5000 API requests in an hour).” – paddy_m
“I think GitHub shipping Copilot while suffering availability issues is a rational choice because they get more measurable business upside from a flashy AI product than from another uptime graph.” – hrmtst93837
These three themes—reliability concerns, the push toward self‑hosting, and the disruption of modern CI/AI workflows—capture the core of the discussion.