# Increased Latency and Failures for SSH Git Operations

- Provider: [GitHub](https://down.guide/github)
- Level: confirmed
- Impact: Degraded
- lasted 1h 46m
- started 2026-05-05 16:49 UTC
- Git Operations
- id: DWN-a8b7db83a8
- Official page: https://stspg.io/x8fvngz3t6ck

## Updates from GitHub
### 2026-05-05 16:49 UTC: investigating
We are investigating reports of impacted performance for some GitHub services.

### 2026-05-05 16:54 UTC: monitoring
Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact.

### 2026-05-05 17:23 UTC: investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.

### 2026-05-05 17:26 UTC: investigating
We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place.

### 2026-05-05 18:25 UTC: monitoring
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

### 2026-05-05 18:35 UTC: monitoring
We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.

### 2026-05-05 18:35 UTC: resolved
Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones, were not affected. 
The impact was caused by reduced SSH capacity at one of our data center sites. During a period of high traffic, the remaining hosts became overloaded, leading to connection exhaustion and some failures for SSH-based operations. 
Additional capacity was provisioned to expand SSH capacity and resolve the incident. The expanded capacity was fully online by 18:18 UTC. 
To reduce the likelihood of similar incidents, we will implement faster scaling solutions for SSH infrastructure and improved alerting for host availability and capacity thresholds.

---
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://sazabi.com/?utm_source=down-guide&utm_medium=markdown).