已歸檔的官方INCIDENT

Incident with Actions

GitHub · 最近儲存的提供方狀態:resolved

當前服務報告 →

官方來源文字以原始語言顯示。

這是歷史證據。

最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整,事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。

已儲存事件詳情

提供方狀態
resolved
提供方影響程度
major
提供方記錄建立時間
29 Jul 2026, 15:26:24 UTC
提供方記錄更新時間
30 Jul 2026, 01:28:07 UTC
提供方明確報告的開始時間
29 Jul 2026, 15:26:24 UTC
提供方明確報告的結束時間
29 Jul 2026, 16:00:54 UTC

提供方報告的受影響元件

  • Actions br0l2tvcx85d

這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。

記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。

已儲存修訂中的提供方更新

最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。

  1. resolved

    On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  2. monitoring

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  3. investigating

    We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  4. investigating

    We are investigating reports of degraded availability for Actions

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到