Regression in windows runners for public repositories
Incident
Report for GitHub
Resolved
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.
Update
At 23:45 UTC we applied a mitigation to take remaining impacted capacity offline and are seeing improvement. We will update again once we've confirmed the issue is resolved.
Update
Our investigation into GitHub Actions 4 Core Windows runner failures in public repositories is ongoing.
If you have a failing GitHub Actions run, please retry it and it is likely to succeed.
If you have a failing GitHub Actions run, please retry it and it is likely to succeed.
Update
We're continuing to investigate failures in GitHub Actions 4 Core Windows runners in public repositories.
If you have a failing GitHub Actions run, please retry it and it is likely to succeed.
If you have a failing GitHub Actions run, please retry it and it is likely to succeed.
Update
Rollback has been completed, but we are still seeing failures on about 11% of GitHub Actions runs on 4 Core Windows runners in public repositories.
If your workflow fails to start, try re-running and it is likely to work a second time.
If your workflow fails to start, try re-running and it is likely to work a second time.
Update
Mitigation for failing GitHub Actions jobs on 4-Core Windows runners is still being mitigated. You should start to see more runs succeeding.
If you do see failing runs, please retry and they might succeed.
If you do see failing runs, please retry and they might succeed.
Update
We've applied a mitigation to unblock running Actions. A regression occurred for Windows runners in public repositories which caused Actions workflows to fail. A mitigation is in place and customers should expect to see resolution soon.
If you have a failing Actions workflow on a Windows runner, please retry and it is likely to work.
If you have a failing Actions workflow on a Windows runner, please retry and it is likely to work.
Investigating
We are investigating reports of impacted performance for some GitHub services.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe