Outage in GitHub
Incident with Actions
Resolved MajorIncident Report
Summary AI Generated
GitHub Actions experienced degraded performance for 3.8 hours, with elevated queue times and job failures primarily affecting hosted runners in the East US region, impacting 8-10% of runs. The incident was caused by issues with GitHub's compute provider and affected both standard hosted runners and hosted runners with private networking. GitHub resolved the issue by applying mitigations for standard runners and working with their compute provider to restore capacity, with private networking users able to failover to other regions during the outage.
We are investigating reports of degraded availability for Actions
Components affected
GitHub ActionsTrusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
1 day ago - at 05/05/2026 05:26PM
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.
INVESTIGATING
1 day ago - at 05/05/2026 05:11PM
Actions is experiencing degraded performance. We are continuing to investigate.
INVESTIGATING
1 day ago - at 05/05/2026 05:11PM
Standard hosted runners have now reached full recovery. Hosted Runners with Private Networking in the East US region remain degraded as we continue working with our compute provider to restore capacity. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
INVESTIGATING
1 day ago - at 05/05/2026 04:33PM
We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
INVESTIGATING
1 day ago - at 05/05/2026 03:54PM
We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
INVESTIGATING
1 day ago - at 05/05/2026 03:12PM
We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
INVESTIGATING
1 day ago - at 05/05/2026 02:14PM
We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different Azure region to mitigate the issue.
INVESTIGATING
1 day ago - at 05/05/2026 01:48PM
We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs
INVESTIGATING
1 day ago - at 05/05/2026 01:37PM
We are investigating reports of degraded availability for Actions
Latest GitHub outages
Incident with Pull Requests - about 13 hours ago
Disruption with some GitHub services - about 17 hours ago
Incident with Actions, we are investigating reports of degraded availability - about 21 hours ago
Incident with Issues and Webhooks - 3 days ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
