GitHub, a renowned global online development platform, was recently impacted with its “Pull” services timing out. The exact reason for the sudden degradation of service is not clear at the moment, but the platform identified an issue with its caching infrastructure and was working to mitigate the issue. The platform also advised that they were conducting an internal investigation to understand the root cause behind the issue.
The development platform said that it’s “investigating reports of degraded availability for Issues and Pull Requests.” To elaborate on the issue, developers use Pull requests to propose changes to any project. As a result, If pull requests are disabled/not working, it might be difficult for users/developers to track project changes, control project quality, and collaborate on different projects. Similarly, ‘Issues’ down, made it difficult for the users to track tasks, begin bug fixes, and manage other items such as code quality in any GitHub project.
Several users who were impacted by the service outage moved to DownDetector, which is a platform that is used to track and report live outages. These problems were tagged as a “major outage” and GitHub is yet to provide more information on the regions and number of users affected by this outage and the extent of the incident. The platform updated that it had to fail over one of its primary caching hosts to mitigate the issue, and users would experience some temporary service disruptions until that process was complete. The incident was confirmed to be resolved after completing the fail-over, and the platform confirmed that the services were operating normally.
In early May 2023, GitHub had most of its primary services affected for three days, causing widespread database connection and authentication failures for up to ten hours.
