Resolved
GitHub · degraded service
Actions Larger Runner Jobs for some customers may be slow to start
Posted 14 Sep 18:40 UTC, last seen today 11:33 UTC.
What it affected
As the provider names itWhat the provider posted
Newest first- 14 Sep 19:35 UTCResolvedOn 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, 5.7% of larger-runner jobs were affected. 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. 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.
- 14 Sep 19:01 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
- 14 Sep 18:40 UTCInvestigatingWe are investigating reports of impacted performance for some GitHub services.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Hyperdrive Degraded Performance
- Anthropic (Claude) Degraded functionality for Claude Cowork on Windows
Earlier incidents in the 14 days before
- GitHub: Incident with several GitHub ServicesService incident · 13 Sep
- GitHub: Degradation in repos contents APIService incident · 4 Sep
- GitHub: Disruption with Copilot Code ReviewService incident · 4 Sep
- GitHub: Incident with Grok Copilot AI Model ProviderService incident · 3 Sep
- GitHub: Delays in commit processingService incident · 1 Sep
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitHub: its changes, known issues and incidents on one timeline.