GitHub outage on August 26, 2026: Incident with Actions and Pull Requests
GitHub reported an incident affecting GitHub for 1 hour 30 minutes on 26 August 2026, from 22:56 to 00:26 UTC.
Resolved
Official incident reported by GitHub
- Started
- 22:56
- 26 Aug 2026 UTC
- Resolved
- 00:26
- 27 Aug 2026 UTC
- Duration
- 1h 30m
- 1 hour 30 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 6
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Incident with Actions and Pull Requests
-
Official
Investigating
We are investigating reports of degraded performance for Actions and Pull Requests
-
Official
Investigating
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
-
Official
Investigating
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
-
Official
Investigating
We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.
-
Official
Monitoring
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
Official
Resolved
On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our...
"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.