Minor impactResolvedDevOps

GitHub incident: Incident with Pull Requests, Issues, Git Operations and API Requests

GitHub reported this minor-impact incident on its official status page on May 27, 2026, 12:10 UTC. It was resolved after 1h 6m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 27, 2026, 12:10 UTC
started
May 27, 2026, 13:16 UTC
resolved
1h 6m
duration
Minor
impact
  1. resolvedMay 27, 2026, 13:16 UTC

    On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates (3.5% of pushes via HTTPS and 0.2% of pushes via SSH failed; no fetches/clones failed). An internal analytics component generated unexpectedly high load, which caused CPU saturation on the underlying infrastructure. This led to cascading slowdowns and errors across services that depend on Git operations. The issue was mitigated by stopping the offending component. Services began recovering shortly after mitigation and were fully restored by 13:16 UTC. We are taking steps to add resource limits and kill switches for internal analytics components to prevent similar issues in the future.

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 27, 2026: Incident with Pull Requests, Issues, Git Operations and API Requests · APIStatus.watch