GitHub Copilot · 78d ago
Incident with GraphQL API Requests
ResolvedYes — GitHub Copilot had a problem on August 11, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “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.”
Timeline
Started: 8/11/2026, 2:50:40 PM
Last update: 8/12/2026, 7:30:45 PM
Resolved: 8/11/2026, 8:06:56 PM
Affected: brv1bkgrwx7q
Updates
resolved
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.
8/11/2026, 8:06:56 PM
monitoring
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.
8/11/2026, 8:06:50 PM
monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
8/11/2026, 4:49:34 PM
investigating
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.
8/11/2026, 4:49:24 PM
investigating
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
8/11/2026, 3:28:44 PM
investigating
We are investigating reports of degraded performance for API Requests
8/11/2026, 2:50:40 PM
More GitHub Copilot incidents
- Delayed Actions status check results — resolved, 6d ago
- Disruption with some Copilot services — resolved, 19h ago
- Grok 4.6 and Grok 4.7 Service Issues — resolved, 5d ago
- Elevated 404s for GitHub App s2s tokens in git/API — resolved, 2d ago
- Incident with Actions, Issues, API Requests and Pull Requests — resolved, 3d ago
- Disruption with Dependabot Alerts — resolved, 6d ago