Developers on Hacker News are voicing a growing frustration with GitHub's reliability since Microsoft’s 2018 acquisition. Recent uptime charts show the platform slipping from green to orange and red zones, while the missing status page leaves users guessing during outages. The sentiment is that GitHub has morphed from a vibrant community hub into a sluggish, corporate‑run service.

Critics point to the so‑called “Copilot circle of hell” and bloated GitHub Actions as evidence of over‑engineering. In response, many are migrating to federated forges such as Codeberg, the community‑driven Forgejo instance, or self‑hosted solutions like Gitea. Larger teams often opt for GitLab, despite its heavier footprint, while Bitbucket remains a less favored corporate alternative.

The exodus underscores a fundamental reminder: Git itself remains a decentralized tool independent of any hosting provider. Developers can clone repositories over SSH or shift to lighter platforms without sacrificing core functionality. As the community fragments, the practical takeaway is clear—avoid reliance on a single, corporate‑owned forge and keep migration paths ready.

For teams unwilling to self‑host, Codeberg offers a nonprofit model with straightforward import tools, while Tangled provides experimental AT‑protocol integration for solo projects. Gitea’s managed cloud service remains the closest drop‑in replacement for existing workflows. Ultimately, the market now offers several viable forks, giving developers a way out of the increasingly unstable Microsoft‑run environment.