GitHub outage renews reliability concerns

GitHub.com suffered a broad service degradation that disrupted pull requests, issues, Actions, git operations, API requests, Pages and webhooks before the incident was marked resolved. Users reported unicorn error pages, failed diffs, unavailable merge status, rate-limited action downloads and intermittent 404 responses on valid repositories.

GitHub’s status update cited an approximate 20% error rate across multiple experiences, while many users described some workflows as effectively unusable. Developers debated whether AI coding tools are overwhelming the platform, citing claims that GitHub activity rose from 1 billion commits in 2025 to 275 million per week, on pace for 14 billion this year if growth remains linear.

Reliability concerns extended beyond the immediate outage. Some users argued that free-tier activity should be rate limited or priced differently, while others blamed Azure migration, Microsoft management or long-standing uptime problems. Several teams discussed moving CI/CD and repository hosting to GitLab, Forgejo, Gitea, Codeberg, Tangled, Buildkite or self-hosted infrastructure, with mirroring and decoupled pipelines emerging as recurring mitigation strategies.