GitHub incident: Incident with GraphQL API Requests

Affected components

• API Requests

1. resolvedJul 27, 2026, 04:09 UTC

   On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or altered. Other GitHub services were not affected.<br /><br />The errors were traced to a single group of servers handling a share of GraphQL API traffic. Application processes on that group intermittently closed connections before completing responses. Impact ended at 03:52 UTC on July 27 when those processes were replaced, and we resolved the incident at 04:09 UTC on July 27 after confirming error rates had returned to normal.<br /><br />We are still investigating why those processes closed connections, and that work is being carried out by the

2. monitoringJul 27, 2026, 04:09 UTC

   The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

3. investigatingJul 27, 2026, 03:53 UTC

   We are investigating reports of degraded performance for API Requests

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.

• RevenueCat: Problems connecting to Apple servicesMajor · Jul 26, 2026, 23:06 UTC
• Akamai: Bot Manager false positive issuesMinor · Jul 27, 2026, 01:46 UTC

How often does GitHub have incidents?

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