Minor impactResolvedDevOps

GitHub incident: Incident with GraphQL API Requests

GitHub reported this minor-impact incident on its official status page on Aug 11, 2026, 14:50 UTC. It was resolved after 5h 16m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Aug 11, 2026, 14:50 UTC
started
Aug 11, 2026, 20:06 UTC
resolved
5h 16m
duration
Minor
impact

Affected components

  • API Requests
  1. resolvedAug 11, 2026, 20:06 UTC

    On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. <br /><br />This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck. <br /><br />We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future.

  2. monitoringAug 11, 2026, 20:06 UTC

    We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.

  3. monitoringAug 11, 2026, 16:49 UTC

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

  4. investigatingAug 11, 2026, 16:49 UTC

    We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.

  5. investigatingAug 11, 2026, 15:28 UTC

    We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information

  6. investigatingAug 11, 2026, 14:50 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.

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

GitHub incident on Aug 11, 2026: Incident with GraphQL API Requests · APIStatus.watch