Incident with GraphQL API Requests

Timeline

1. 12 Aug · 19:30 UTC 🟡 Resolved atom

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

2. 12 Aug · 19:30 UTC 🟡 Resolved atom

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