Live / Incidents / GitHub Copilot
GitHub Copilot: Actions delays in starting runs
GitHub Copilot · github.comImpact: minorResolved2026-08-24 14:34 UTC
Public — what happened
Summary
On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic reba
Timeline
- Started — 2026-08-24 13:56 UTC
- Last update — 2026-08-24 14:34 UTC
- Resolved — 2026-08-24 14:34 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 →