Incident with GraphQL API Requests

What to do

• Check whether you use GitHub API Requests. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 16m it lasted.

  Anything that failed between 2026-08-11 14:50 UTC and 2026-08-11 20:06 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 6

1. investigatingAug 11, 2026, 2:50 PM UTC

   We are investigating reports of degraded performance for API Requests

   provider

2. investigatingAug 11, 2026, 3:28 PM 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

   provider

3. investigatingAug 11, 2026, 4:49 PM 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.

   provider

4. monitoringAug 11, 2026, 4:49 PM UTC

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

   provider

5. monitoringAug 11, 2026, 8:06 PM 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.

   provider

6. resolvedAug 11, 2026, 8:06 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.