Incident with GraphQL API Requests
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 11 Aug 2026, 14:50:40 UTC
- Provider record updated
- 12 Aug 2026, 19:30:45 UTC
- Explicit provider start
- 11 Aug 2026, 14:50:40 UTC
- Explicit provider end
- 11 Aug 2026, 20:06:56 UTC
Affected components reported by the provider
- API Requests
brv1bkgrwx7q
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for API Requests
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC