GitHub Copilot incident

Actions Larger Runner Jobs for some customers may be slow to start

Minor Resolved Upstream link ↗

Started

September 14, 2026 at 06:40 PM UTC

Duration

55 min

Resolved

September 14, 2026 at 07:35 PM UTC

Updates timeline

  1. Investigating

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

  2. Monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. 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.

Get an email the next time GitHub Copilot goes down

Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader