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 的已儲存修訂中觀察到