GitHub outage on September 14, 2026: Actions Larger Runner Jobs for some customers may be slow to start
GitHub reported an incident affecting GitHub for 55 minutes on 14 September 2026, from 18:40 to 19:35 UTC.
Resolved
Official incident reported by GitHub
- Started
- 18:40
- 14 Sep 2026 UTC
- Resolved
- 19:35
- 14 Sep 2026 UTC
- Duration
- 55m
- 55 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 3
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Actions Larger Runner Jobs for some customers may be slow to start
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
Official
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, 5.7% of larger-runner jobs were affected. 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. 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.
"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.