Incident with Github.com [resolved]

Article summary

GitHub experienced an incident where users received an error message stating that no server was available to service their request. The issue was initially not reported on GitHub's status page, but an incident was later declared. Users reported various issues, including being unable to push releases, merge pull requests, and load entire repositories. The incident highlights the reliance on GitHub and the potential consequences of downtime.

Main themes

• GitHub downtime
• CI/CD pipeline reliability
• Self-hosted alternatives
• Compute resource costs
• Reliability concerns
• Trade-offs between hosted and self-hosted services

What commenters say

• Some users are considering replacing GitHub as their CI/CD pipeline due to reliability concerns.
• Self-hosted alternatives, such as GitLab and Gitea, are being explored as potential replacements.
• The cost of compute resources for self-hosted CI runners can be a significant factor in the decision-making process.
• Others have had positive experiences with self-hosted solutions, citing reliability and flexibility as advantages.
• Some users believe that GitHub's reliability issues are not unique to the platform and that self-hosted solutions can also experience downtime.
• The incident has sparked discussions about the trade-offs between using a hosted service like GitHub and self-hosting a CI/CD pipeline.
• Some users are satisfied with their current self-hosted solutions and do not see a need to switch to a hosted service like GitHub.
• The reliability of GitHub is being questioned, with some users feeling that the platform is not as reliable as they had expected.