GitHub Actions and Pages are experiencing degraded availability
Points and comments are a snapshot, not live.
GitHub Actions and Pages experienced a major degradation affecting workflows, webhooks, and self-hosted runners.
An incident on August 6-7, 2026 caused widespread failures in GitHub Actions, Pages, Copilot code review, Copilot coding agent, and GitHub Enterprise Importer migrations. Workflows failed to start or complete, webhook deliveries were delayed or throttled, and self-hosted runners could not pick up jobs. Some Actions Runner Controller (ARC) runner pods became stuck idle. Mitigations included draining queues, deploying fixes for invalid job assignments, and achieving 99% job completion success rates. Some push and pull request events lost during the incident cannot be replayed automatically; users may need to retrigger them manually.
What commenters are saying
Commenters expressed frustration at the frequency and severity of GitHub outages, with several noting this as the sixth incident in August. Two camps emerged: those blaming Microsoft's prioritization of AI/Copilot features over core reliability, and those arguing GitHub has never been truly reliable. Several users highlighted that self-hosted runners were also affected because they depend on GitHub's scheduler. A specific complaint noted that error messages during the outage were unhelpful, suggesting they should clearly indicate "no runner available" rather than vague failures. Some commenters discussed alternatives like Forgejo, GitLab, and upcoming forges, but found the PR/review experience lacking.