已归档的官方INCIDENT

Degradation in repos contents API

GitHub · 最近保存的提供方状态：resolved

官方来源文字以原始语言显示。

这是历史证据。

最近保存的事件状态不是当前服务状态。来源列表可能不完整，事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。

已保存事件详情

提供方在此已保存修订中明确列出没有受影响组件。

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

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

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

resolved04 Sep 2026, 22:23:34 UTC
On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.<br /><br />The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.<br /><br />We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.
在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
investigating04 Sep 2026, 22:02:15 UTC
We are investigating reports of impacted performance for some GitHub services.
在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到