GraphQL API请求事件
2026年8月11日,UTC时间14:00至16:00期间,GraphQL API服务出现降级,客户遇到高于正常水平的超时。平均超时率为0.06%,峰值时占路由至该服务请求的0.14%。<br /><br />此问题源于我们一个站点利用率增加,导致依赖项间资源争用,进而引发GraphQL请求超时增多。我们通过增加容量以缓解容量瓶颈,从而减轻了事件影响。<br /><br />我们正致力于改进监控,以便在扩容之外,主动减少高消耗请求的影响;同时,我们将提升对此类问题的检测和缓解速度,以防未来再次发生。
原文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.
我们已识别并缓解了影响GraphQL API请求的错误率上升问题。为提升服务容量而部署的修复程序已生效,错误率已恢复正常水平。我们正在处理此事件。
原文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.
影响API请求的服务降级问题已得到缓解。我们正在持续监控以确保稳定性。
原文The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
GraphQL API请求已恢复到正常基线水平。我们将继续调查此次事件期间出现的错误。
原文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.
我们正在调查有关GraphQL API请求错误率小幅上升的报告。我们正在努力提升容量,并继续调查错误增加的原因。一旦获得更多信息,我们将提供进一步更新。
原文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
我们正在调查有关API请求性能下降的报告。
原文We are investigating reports of degraded performance for API Requests
关于这些数据
事件从哪来?
全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。