Disruption with some GitHub services

Updates timeline

1. Investigating Apr 28, 01:59 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. Monitoring Apr 28, 01:59 PM UTC

   Actions is experiencing capacity constraints with hosted ubuntu-latest and ubuntu-24.02, leading to high wait times. Other hosted labels and self-hosted runners are not impacted.

3. Investigating Apr 28, 02:02 PM UTC

   Actions is experiencing degraded performance. We are continuing to investigate.

4. Investigating Apr 28, 02:49 PM UTC

   We're still investigating the root cause for run start delays and failures for Actions hosted Ubuntu jobs, around 5% of jobs are impacted as of now.

5. Investigating Apr 28, 03:20 PM UTC

   We've applied a mitigation to unblock running Actions. We're continuing to monitor.

6. Investigating Apr 28, 03:41 PM UTC

   Currently less than 2% of hosted ubuntu-latest and ubuntu-24.04 runs are delayed or failing. We are continuing to monitor for full recovery.

7. Investigating Apr 28, 04:36 PM UTC

   Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.

8. Monitoring Apr 28, 05:08 PM UTC

   Actions is operating normally.

9. Resolved Apr 28, 05:09 PM UTC

   On April 28, 2026, from approximately 12:41 UTC to 17:09 UTC, GitHub Actions jobs using Standard Ubuntu 22 and Ubuntu 24 hosted runners experienced run start delays. Approximately 8% of hosted runner jobs using Ubuntu 22 and Ubuntu 24 experienced delays greater than 5 minutes or failures. Larger and self-hosted runners were not impacted.<br /><br />This was caused by a performance regression introduced in the VM reimage process. That reimage delay lowered the overall capacity of runners available to pick up new jobs. This was mitigated with a rollback to a known good image version.<br /><br />We are addressing the core issue with reimage performance and improving the granularity of reimage telemetry across our services and our compute provider to more quickly diagnose similar issues in the future. Finally, we are evaluating other rollout changes to automatically detect similar regressions.