Resolved
GitHub · degraded service
Actions delays in starting runs
Posted 24 Aug 13:56 UTC, last seen 5 Oct 23:43 UTC.
Unknown
Duration: the provider stated no start
4Updates posted
What it affected
As the provider names itWhat the provider posted
Newest first- 24 Aug 14:34 UTCResolvedOn 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. 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 rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover.
- 24 Aug 14:26 UTCMonitoringThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- 24 Aug 14:22 UTCUpdateFailures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
- 24 Aug 13:56 UTCInvestigatingWe are investigating reports of degraded performance for Actions
Around it
From the sources ChangeIntel reads; a match in time is not a causeEarlier incidents in the 14 days before
- GitHub: Elevated errors on Fable 5 due to upstream providerService incident · 24 Aug
- GitHub: Degraded Git Operations over SSHService incident · 21 Aug
- GitHub: Intermittent failures creating agent tasksService incident · 20 Aug
- GitHub: Intermittent failures in runner group and runner-related permissions pagesService incident · 18 Aug
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.