Incident with Actions, Pages, and Webhooks
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
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, Issues, API Requests and Pull Requests
We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.We mitigated the issue and all services have recovered.
Delayed Actions status check results
As of 07:27 UTC, Actions results are delivering within normal SLOs again.Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future.
Project updates delayed
The degradation has been mitigated. We are monitoring to ensure stability.
Incident with Actions Results
We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
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.