GitHub experienced a minor incident on April 28, 2026 affecting Actions, lasting 3h 9m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 28, 2026, 01:59 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring Apr 28, 2026, 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.
- investigating Apr 28, 2026, 02:02 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 28, 2026, 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.
- investigating Apr 28, 2026, 03:20 PM UTC
We've applied a mitigation to unblock running Actions. We're continuing to monitor.
- investigating Apr 28, 2026, 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.
- investigating Apr 28, 2026, 04:36 PM UTC
Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.
- monitoring Apr 28, 2026, 05:08 PM UTC
Actions is operating normally.
- resolved Apr 28, 2026, 05:09 PM UTC
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.