Incident with Github.com [resolved]
Points and comments are a snapshot, not live.
GitHub suffered a widespread outage on August 17, 2026, impacting numerous core services.
On August 17, 2026, GitHub experienced a major incident affecting Git Operations, Webhooks, API Requests, Issues, Pull Requests, Actions, Pages, and Copilot. Error rates reached approximately 20% for web and API traffic, with archive/download errors around 50%. SAML/OIDC authentication, SCIM, and Team Sync were also impacted. The incident was declared at 13:40 UTC and resolved by 21:15 UTC. GitHub identified the problematic component and applied mitigations, with a detailed root cause analysis to follow. Copilot authentication failures lingered after the main recovery.
What commenters are saying
Commenters expressed frustration with GitHub's reliability and its status page, which initially showed all green despite widespread outages. Many joked about the predictability of disruptions, with one noting it was Monday. A significant thread discussed replacing GitHub for CI/CD, with advocates for self-hosted GitLab, Gitea/Forgejo, and Buildkite. Others defended the convenience of GitHub Actions for cross-platform builds and highlighted that third-party CI services often fail when GitHub's API is down.