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件の異なる更新を表示します。同じ提供元時刻の文章変更も別に保持します。
- 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 - monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
保存リビジョンでの確認：06 Oct 2026, 13:58:39 UTC - 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 - investigating
We are investigating reports of degraded availability for Actions
保存リビジョンでの確認：06 Oct 2026, 13:58:39 UTC