Incident with API Requests
Incident
Report for GitHub
Resolved
On February 11, 2026, between 13:51 UTC and 17:03 UTC, the GraphQL API experienced degraded performance due to elevated resource utilization. This resulted in incoming client requests waiting longer than normal, timing out in certain cases. During the impact window, approximately 0.65% of GraphQL requests experienced these issues, peaking at 1.06%.
The increased load was due to an increase in query patterns that drove higher than expected resource utilization of the GraphQL API. We mitigated the incident by scaling out resource capacity and limiting the capacity available to these query patterns.
We're improving our telemetry to identify slow usage growth and changes in GraphQL workloads. We’ve also added capacity safeguards to prevent similar incidents in the future.
The increased load was due to an increase in query patterns that drove higher than expected resource utilization of the GraphQL API. We mitigated the incident by scaling out resource capacity and limiting the capacity available to these query patterns.
We're improving our telemetry to identify slow usage growth and changes in GraphQL workloads. We’ve also added capacity safeguards to prevent similar incidents in the future.
Update
We've observed recovery for the GraphQL service latency.
Update
We're continuing to remediate the service degradation and scaling out to further mitigate the potential for latency impact.
Update
We've identified a dependency of GraphQL that is in a degraded state and are working on remediating the issue.
Update
We're investigating increased latency for GraphQL traffic.
Investigating
We are investigating reports of degraded performance for API Requests
This incident affected: API Requests.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe