Incident with Actions
GitHub · 最近儲存的提供方狀態：resolved
官方來源文字以原始語言顯示。
最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整，事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。
已儲存事件詳情
- 提供方狀態
- resolved
- 提供方影響程度
- major
- 提供方記錄建立時間
- 18 Aug 2026, 09:36:40 UTC
- 提供方記錄更新時間
- 24 Aug 2026, 05:55:48 UTC
- 提供方明確報告的開始時間
- 18 Aug 2026, 09:36:40 UTC
- 提供方明確報告的結束時間
- 18 Aug 2026, 10:23:23 UTC
提供方報告的受影響元件
提供方在此已儲存修訂中明確列出沒有受影響元件。
這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。
記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。
已儲存修訂中的提供方更新
最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。
- resolved
On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />These issues were caused by failures in backend requests resolving essential metadata for starting Larger Runner workflow runs and for reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused to prevent recurrence of previous incidents that had been triggered by this operation. <br /><br />We mitigated the issues by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. The relevant service is also in the process of being replaced as part of our availability and scale work, bringing this authentication path and secret management in line with patterns across all GitHub services.
在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到 - investigating
We are investigating reports of impacted performance for some GitHub services.
在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到