Minor impactResolvedDevOps

GitHub incident: Incident with high errors on Git Operations

GitHub reported this minor-impact incident on its official status page on May 11, 2026, 14:25 UTC. It was resolved after 8 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 11, 2026, 14:25 UTC
started
May 11, 2026, 14:33 UTC
resolved
8 min
duration
Minor
impact
  1. resolvedMay 11, 2026, 14:33 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on May 11, 2026: Incident with high errors on Git Operations · APIStatus.watch