GitHub outage on August 24, 2026: Actions delays in starting runs
GitHub reported an incident affecting GitHub for 38 minutes on 24 August 2026, from 13:56 to 14:34 UTC.
Resolved
Official incident reported by GitHub
- Started
- 13:56
- 24 Aug 2026 UTC
- Resolved
- 14:34
- 24 Aug 2026 UTC
- Duration
- 38m
- 38 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 4
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Actions delays in starting runs
-
Official
Investigating
We are investigating reports of degraded performance for Actions
-
Official
Investigating
Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
-
Official
Monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
Official
Resolved
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. 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.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.