GitHub reported this critical-impact incident on its official status page on Nov 10, 2026, 16:10 UTC. It was resolved after 1h 44m.
Right now GitHub is degraded. Live GitHub status →
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.
Actions is operating normally.
Pull Requests is experiencing degraded performance. We are continuing to investigate.
We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service.
Actions is experiencing degraded availability. We are continuing to investigate.
We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more.
Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate.
We are investigating reports of degraded performance for Actions and Pull Requests
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 28 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history