GitHub appears to be struggling with measly three nines availability (theregister.com)

Article summary

GitHub has been experiencing service instability, with slowdowns, outages, and issues with its Copilot feature. The company's status page has been changed, making it harder to track the availability of its services. GitHub's Service Level Agreement for Enterprise Cloud customers specifies 99.9 percent uptime, but the company does not guarantee this for all users. The outages have raised concerns about the reliability of cloud services and the need for customers to plan for downtime.

Main themes

• GitHub outages
• Cloud service reliability
• Service Level Agreements
• Microsoft acquisition impact
• CI/CD pipeline issues

What commenters say

• The migration to Azure is a monumental undertaking that will likely lead to worse reliability before it improves.
• GitHub's focus on adding new features has come at the cost of reliability and stability.
• The company's decision to switch to Azure will not necessarily improve its reliability, and may even introduce new issues.
• Self-hosting CI/CD pipelines is a viable alternative to relying on GitHub Actions, which has been experiencing outages and issues.
• The user experience of GitHub has deteriorated, particularly with regards to code review and search functionality.
• Some users have lost faith in GitHub's vision and have switched to alternative platforms, such as self-hosted Jenkins or GitLab.
• The acquisition by Microsoft has had a negative impact on GitHub's reliability and overall quality of service.
• GitHub's issues are not unique to the company, but rather a symptom of a larger problem with cloud services and the prioritization of growth over reliability.