Skip to content
GitHub · Developer toolsAug 11, 2026, 14:50 UTC

Incident with GraphQL API Requests

MinorNot disclosedUpdated 20h ago
Aug 11, 14:50 UTCAug 11, 20:06 UTC
Duration
5h 16m
Impact
Minor
Root cause
Not disclosed
GitHub, 90 days
68 incidents
Affected
API Requests
Status page

Final update

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. 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. 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.

Timeline

  1. Resolved · Aug 11, 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. 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. 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. Monitoring · Aug 11, 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. Monitoring · Aug 11, 16:49 UTC
    The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
  4. Investigating · Aug 11, 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. Investigating · Aug 11, 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. Investigating · Aug 11, 14:50 UTC
    We are investigating reports of degraded performance for API Requests

More from GitHub

Full history
StartedIncidentDuration
Sep 2310:11 UTCIncident across several servicesOngoing
Sep 2022:13 UTCIncident with Pull Requests1h 9m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.