Incident with Pages - Deployment Lag
GitHub · 最近保存的提供方状态：resolved
官方来源文字以原始语言显示。
最近保存的事件状态不是当前服务状态。来源列表可能不完整，事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。
已保存事件详情
- 提供方状态
- resolved
- 提供方影响程度
- minor
- 提供方记录创建时间
- 06 Aug 2026, 15:03:55 UTC
- 提供方记录更新时间
- 10 Aug 2026, 21:16:18 UTC
- 提供方明确报告的开始时间
- 06 Aug 2026, 15:03:55 UTC
- 提供方明确报告的结束时间
- 06 Aug 2026, 16:22:59 UTC
提供方报告的受影响组件
- Pages
vg70hn9s2tyj
这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。
记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。
已保存修订中的提供方更新
最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。
- resolved
On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. <br /><br />At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC. <br /><br />Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments. <br /><br />We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.
在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到 - monitoring
The degradation affecting Pages 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 Pages
在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到