Incident with GraphQL API Requests
GitHub · 最近儲存的提供方狀態：resolved
官方來源文字以原始語言顯示。
最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整，事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。
已儲存事件詳情
- 提供方狀態
- 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 條不同更新。同一提供方時間的文字修訂單獨保留。
- resolved
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 的已儲存修訂中觀察到 - monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到 - investigating
We are investigating reports of degraded performance for API Requests
在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到