GitHub outage on October 13, 2026: [Retroactive] Actions workflow run logs delayed
GitHub reported an incident affecting GitHub for 1 minute on 13 October 2026, from 20:30 to 20:30 UTC.
Resolved
Official incident reported by GitHub
- Started
- 20:30
- 13 Oct 2026 UTC
- Resolved
- 20:30
- 13 Oct 2026 UTC
- Duration
- <1m
- 1 minute
- Impact
- Minor
- as rated by GitHub
- Updates
- 1
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
[Retroactive] Actions workflow run logs delayed
-
Official
Resolved
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.
"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.