# Incident with Git Operations

- Provider: [GitHub](https://down.guide/providers/github)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1h 44m
- started 2026-11-03 20:57 UTC
- Git Operations
- GitHub states the impact was 2026-11-03 15:00 to 22:37 UTC (7h 37m)
- id: DWN-c61ea0cc46
- Official page: https://stspg.io/n478rfsspcmr

## Updates from GitHub
### 2026-11-03 20:57 UTC: investigating
We are investigating reports of degraded performance for Git Operations

### 2026-11-03 21:37 UTC: investigating
We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.

### 2026-11-03 22:05 UTC: investigating
Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.

### 2026-11-03 22:37 UTC: investigating
We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor.

### 2026-11-03 22:37 UTC: monitoring
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

### 2026-11-03 22:41 UTC: resolved
On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. 
This was due to a buildup of excess connections on the hosts that serve Git HTTPS traffic, which saturated their network capacity and caused slow and failed responses for all clients served by those hosts. 
We mitigated the incident by blocking a client traffic pattern at our load balancers and reloading them, which released the excess connections. The block also prevented some users of one third-party integration from performing Git operations over HTTPS until we removed it on November 4 at 13:26 UTC. 
We are working to alert on sustained Git HTTPS latency sooner and make load balancer mitigations take effect on existing connections immediately.

From the builder: does your app depend on GitHub? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=github) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention GitHub.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-c61ea0cc46), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.