Another GitHub outage in the same day (githubstatus.com)

Article summary

GitHub experienced another outage, affecting issues, actions, and Git operations. The incident has been resolved, but it has sparked discussion about the reliability of the platform. Some users are considering moving to self-hosted alternatives like GitLab or Forgejo. The outage has also raised concerns about the impact of Microsoft's ownership on GitHub's performance.

Main themes

• GitHub outages
• Self-hosted alternatives
• Microsoft ownership
• Reliability concerns
• Cloud services

What commenters say

• Some users are switching to self-hosted Git solutions like GitLab or Forgejo due to GitHub's frequent outages.
• The reliability of GitHub has decreased since its acquisition by Microsoft, leading to frustration among users.
• GitHub's integration of Copilot has been met with criticism, with some users finding it underperforms compared to other AI-powered tools.
• The trend of non-functional software is not unique to GitHub, but rather a broader issue in the tech industry.
• Microsoft's business priorities, such as promoting Copilot, may be compromising the user experience on GitHub.
• The difficulty of migrating away from GitHub due to network effects and engineering challenges is a major obstacle for users considering alternatives.
• Some users believe that the shift to client-side rendering and cloud-based services is contributing to the decline in GitHub's performance.