Live / Incidents / GitHub Copilot
GitHub Copilot: Actions Larger Runner Jobs for some customers may be slow to start
GitHub Copilot · github.comImpact: minorResolved2026-09-14 19:35 UTC
Public — what happened
Summary
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 recu
Timeline
- Started — 2026-09-14 18:40 UTC
- Last update — 2026-09-14 19:35 UTC
- Resolved — 2026-09-14 19:35 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub Copilot against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub Copilot: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub Copilot report →