Users are reporting widespread 504 Gateway Timeouts and 503 Service Unavailable errors when attempting to access GitHub repositories and download software releases. These disruptions are notably occurring even while the official GitHub status page continues to report that all systems are operational, creating a significant gap between official reporting and actual user experience.
Reported Service Disruptions
The original post on Hacker News, linked to the Linux kernel repository, highlights a period where GitHub appeared to be down for many users. Commenters corroborated this, reporting specific 504 Gateway Timeout and 503 Service Unavailable errors when trying to open repository web pages or download tools.
One commenter, writing as shimms, noted that the issue specifically affected release downloads, which broke their continuous integration (CI) systems. Another user, bagels, reported that these failures persisted for over 30 minutes, preventing the use of Terraform and other automated tools.
Discrepancies in Status Reporting
A primary point of contention in the discussion is the inaccuracy of the official status page. Commenters noted that while the page shows 'all good,' many users are still unable to access services, leading to confusion about whether the fault lies with their own networks.
One commenter, skissane, suggested that the status page might only display outages that management deems 'sufficiently major.' Others pointed out that even third-party status trackers might be inaccurate if they rely on the same incident data provided by GitHub.
There is also evidence of inconsistent access; some users reported that they could access the site while logged in, but received 504 errors when logged out, suggesting a potential issue with the Content Delivery Network (CDN) or public-facing infrastructure.
Infrastructure Load and Alternatives
Some participants in the discussion attributed the instability to a massive increase in platform load. One commenter, czarek_pl, cited reports that the number of commits on GitHub increased fivefold over the past year, potentially due to the 'AI revolution' and the resulting demand on infrastructure.
In response to these recurring issues, some commenters suggested moving away from GitHub to avoid the 'liability' of a single point of failure. Suggestions included hosting private repositories on cheap virtual private servers (VPS) or using alternatives like Codeberg, which is described by one commenter as a lightweight, open-source-friendly option.
Unresolved Technical Causes
The specific technical cause of the 504 and 503 errors remains unconfirmed by the provided sources. It is unclear whether the issue is a localized CDN failure, a specific breakdown in the release download infrastructure, or a broader capacity issue related to the reported increase in commit volume.
The discrepancy between the 'all good' status and the reported 504 errors remains a point of uncertainty. Without official confirmation from GitHub, it is impossible to determine if the status page is intentionally filtered or simply failing to capture specific types of service degradation.