Actions Larger Runner Jobs for some customers may be slow to start
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 14 Sep 2026, 18:40:25 UTC
- Provider record updated
- 18 Sep 2026, 23:11:13 UTC
- Explicit provider start
- 14 Sep 2026, 18:40:25 UTC
- Explicit provider end
- 14 Sep 2026, 19:35:48 UTC
Affected components reported by the provider
The provider explicitly listed no affected components in this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- resolved
On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. <br /><br />We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recurring. We have also added alerts for VM-record creation failures associated with this capacity issue.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC