Jul 9, 2026, 04:34 AM → Jul 9, 2026, 01:52 PM · 9h 17m
On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start.<br /><br />At 13:39 UTC, we restored the
Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated.<br /><br />We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog.<br /><br />Customers may see a small rate of API and job failures as the system is recovering.<br /><br />Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.<br /><br />Pages were accessible throughout the incident.
Actions is experiencing degraded availability. We are continuing to investigate.
We're seeing Actions and Pages recovery. <br /><br />For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.<br /><br />GitHub pages builds were also failing during that period, but Pages are still accessible.<br /><br />We are continuing to monitor for full recovery.
Actions is experiencing degraded availability. We are continuing to investigate.
Pages is experiencing degraded performance. We are continuing to investigate.