Increased Latency and Failures for SSH Git Operations

What to do

• Check whether you use GitHub Git Operations. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 46m it lasted.

  Anything that failed between 2026-05-05 16:49 UTC and 2026-05-05 18:35 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 7

1. investigatingMay 5, 2026, 4:49 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. monitoringMay 5, 2026, 4:54 PM UTC

   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.

   provider

3. investigatingMay 5, 2026, 5:23 PM UTC

   Git Operations is experiencing degraded performance. We are continuing to investigate.

   provider

4. investigatingMay 5, 2026, 5:26 PM UTC

   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.

   provider

5. monitoringMay 5, 2026, 6:25 PM UTC

   The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

   provider

6. monitoringMay 5, 2026, 6:35 PM UTC

   We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.

   provider

7. resolvedMay 5, 2026, 6:35 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.