GitHub outage on September 4, 2026: Degradation in repos contents API
GitHub reported an incident affecting GitHub for 21 minutes on 4 September 2026, from 22:02 to 22:23 UTC.
Resolved
Official incident reported by GitHub
- Started
- 22:02
- 4 Sep 2026 UTC
- Resolved
- 22:23
- 4 Sep 2026 UTC
- Duration
- 21m
- 21 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 2
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Degradation in repos contents API
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Resolved
On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC. The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance. We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.
"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.