GitHub outage on November 9, 2026: Incident with Webhooks and Actions
GitHub has reported an incident affecting GitHub since 10:00 UTC on 9 November 2026 (47 minutes so far).
Open
Official incident reported by GitHub
- Started
- 10:00
- 9 Nov 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 47m
- 47 minutes so far
- Impact
- Minor
- as rated by GitHub
- Updates
- 2
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Incident with Webhooks and Actions
-
Official
Investigating
We are investigating reports of degraded performance for Actions and Webhooks
-
Official
Investigating
We're investigating delays in Actions runs start times and webhook deliveries.
"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.