Incident with several GitHub Services
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Is GitHub Actions down?
Check GitHub Actions provider status and notices affecting workflow jobs, hosted runners and automation. Review queue problems separately from GitHub-wide health.
Operational
GitHub lists Actions as operational.
Current Actions incidents
No active incident explicitly naming this component appears in the latest verified source.
Recent resolved Actions incidents
Up to five provider-backed records that explicitly name this component. This is not a complete downtime history or an uptime measurement.
Incident with Actions and Pull Requests
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
Incident with Actions
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
What this status covers
Actions runs workflows such as tests, builds and deployments. Its component status is separate from repository access and Git operations. A workflow can also wait because of runner availability, concurrency settings or an approval.
GitHub Actions jobs stuck in a queue: troubleshooting guide
If you are having a problem
- Open the waiting job and read the reason shown before rerunning it.
- Check whether the job uses GitHub-hosted or self-hosted runners and whether a matching runner is available.
- Check concurrency groups and required approvals. Avoid repeatedly restarting a deployment whose previous outcome is unclear.
A quiet status page does not rule out a new or account-specific issue. Save the error and its time before contacting your administrator or GitHub Support.