Incident with high errors on 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 8m it lasted.

  Anything that failed between 2026-05-11 14:25 UTC and 2026-05-11 14:33 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 2

1. investigatingMay 11, 2026, 2:25 PM UTC

   We are investigating reports of degraded performance for Git Operations

   provider

2. resolvedMay 11, 2026, 2:33 PM UTC

   On May 11th, 2026, between 14:00 UTC and 14:33 UTC, HTTP-based Git read operations were degraded. On average, the error rate was 2.8% and peaked at 7.5% of requests to the service. This was due to resource exhaustion in a networking gateway between GitHub.com’s frontend service for Git operations and a dependency service that performs authentication and authorization. Following the initial spike, the frontend service became stuck in a degraded state in one of our data centers, increasing time to mitigation. We mitigated the incident by scaling the networking gateway and re-deploying the frontend service. To reduce our time to detection and mitigation in the future, we are adding auto-scaling to the networking gateway, and resolving a bug which caused the frontend service to remain degraded.

   provider

Corrections

None so far.

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