Incident with GraphQL API Requests

已保存事件详情

提供方状态

resolved

提供方影响程度

minor

提供方记录创建时间

27 Jul 2026, 03:53:19 UTC

提供方记录更新时间

11 Aug 2026, 16:17:32 UTC

提供方明确报告的开始时间

27 Jul 2026, 03:53:19 UTC

提供方明确报告的结束时间

27 Jul 2026, 04:09:10 UTC

提供方报告的受影响组件

• API Requests brv1bkgrwx7q

这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。

记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。

已保存修订中的提供方更新

最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。

1. resolved27 Jul 2026, 04:09:10 UTC

   On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or altered. Other GitHub services were not affected.<br /><br />The errors were traced to a single group of servers handling a share of GraphQL API traffic. Application processes on that group intermittently closed connections before completing responses. Impact ended at 03:52 UTC on July 27 when those processes were replaced, and we resolved the incident at 04:09 UTC on July 27 after confirming error rates had returned to normal.<br /><br />We are still investigating why those processes closed connections, and that work is being carried out by the team that owns the underlying compute platform. In the meantime we are adding detection and automated mitigation for when a single group of servers behaves differently from its peers.

   在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
2. monitoring27 Jul 2026, 04:09:01 UTC

   The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

   在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
3. investigating27 Jul 2026, 03:53:19 UTC

   We are investigating reports of degraded performance for API Requests

   在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到