GitHub was down for more than two hours, affecting millions of developers

On November 28, according to foreign media reports, Microsoft GitHub experienced a downtime of more than two hours, affecting thousands or even millions of developers who depend on its many services.

According to reports, GitHub began to experience problems around 3:45 pm Eastern Time, including Git operations, API requests, GitHub Actions, GitHub Packages, GitHub Pages, and pull requests. Services were all affected.

"We are investigating a bug affecting GitHub," the event update on the GitHubstatus status page at the time showed. "We are actively investigating this matter and will provide the latest information as soon as possible."

During the downtime, GitHub's official Twitter account continued to update its latest status. From the timeline point of view, the first service that experienced performance degradation was GitHub Actions, which subsequently spread to services such as issue, PR merge and pull, and GitHub Packages. It was not until more than two hours later that the problem was identified and repaired.

GitHub now hosts more than 73 million developers and hosts more than 100 million repositories. The developers and maintainers of these repositories rely on the services provided by GitHub for version control and other project management operations. Therefore, any failure in GitHub will affect a large number of organizations. . Last year, GitHub had a service error and went down for two hours, which caused its service to go offline for a short time.

​The reason for the downtime has not yet been announced, and it has been fully restored.