带有行动的事件

2026年8月6日15:05 UTC至8月7日00:14 UTC期间，GitHub Actions遭遇了可用性降级。事件期间，工作流运行失败或长时间处于排队状态。使用GitHub托管和自托管运行器的客户均受到影响。高峰期，71%的工作流运行遭遇基础设施故障，剩余工作流运行中有75%被延迟超过5分钟。<br /><br />该事件由一次针对内部Actions服务的常规部署触发，该服务负责处理事件并生成Actions作业。部署暴露了现有的容量和并发弱点。随着部署期间Pod被替换，剩余容量饱和，导致服务崩溃，并在多个集群和下游服务中引发连锁影响。<br /><br />这些服务在17:00后通过扩容、限制传入的webhook触发工作以让系统恢复，并增加受影响事件积压的处理能力而得以恢复。<br /><br />随着事件进展，负责将作业分配给运行器的系统中积累了积压工作。由于作业分配服务中的一个潜在缺陷，运行器被分配了已失效的作业，并陷入重试这些作业的困境，无法接手有效工作。<br /><br />第二阶段的影响通过部署变更以防止运行器反复尝试获取无效作业而得到缓解。这些缓解措施使积压队列得以清空，Actions恢复正常运行。<br /><br />事件后，部分Actions Runner Controller（ARC）运行器仍处于卡住状态。事件期间部署的一项缓解措施意外影响了这些运行器，导致部分运行器在手动恢复前一直处于离线状态。我们随后回滚了该变更，并将在即将发布的Runner和ARC版本中添加自动恢复功能。<br /><br />事件期间创建的一些作业也仍处于卡住状态，无法重试或取消。针对这些问题的CLI和UI解决方案已在https://github.com/orgs/community/discussions/204152#discussioncomment-17946043分享。<br /><br />为防止再次发生，我们正在改进受影响服务的部署和容量保障措施，加强事件前状况的监控，提升排队工作和运行器分配的韧性与恢复能力，并为受类似故障条件影响的自托管运行器添加自动恢复功能。我们还在进行额外改进，以降低级联故障风险，并在大规模Actions中断期间加速恢复。

原文On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes. <br /><br />The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services. <br /><br />These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events. <br /><br />As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work. <br /><br />This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation. <br /><br />Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases. <br /><br />Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043. <br /><br />To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.

在事件期间，部分Actions Runner Controller（ARC）运行器Pod陷入空闲状态。受影响用户可使用kubectl删除这些Pod，或重新部署其Actions Runner Controller应用。ARC将自动创建替代运行器。<br /><br />即将发布的Actions Runner和Actions Runner Controller版本将包含自动恢复机制，未来无需这些手动步骤。<br /><br />事件期间，包括推送和拉取请求事件在内的部分工作流触发事件未被处理，且无法自动重放。客户可能需要通过推送新提交、更新拉取请求或在适用情况下手动重新运行工作流来重复触发操作。

原文During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.<br /><br />The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.<br /><br />Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.

我们正在调查有关部分Actions Runner Controller运行器恢复时间超出预期的报告。随着调查的进展，我们将提供最新信息。

原文We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.

故障已缓解。我们正在监控以确保稳定性。

原文The degradation has been mitigated. We are monitoring to ensure stability.

影响Actions和Pages的服务降级问题已得到缓解。我们正在持续监控以确保稳定性。

原文The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

系统范围内的队列已清空，新任务正在按预期处理。针对自托管运行器未接收任务的问题，修复已全面部署。<br /><br />由Webhook触发的Actions工作流已恢复至全吞吐量。GitHub Pages、Copilot代码审查及Copilot编码代理显示恢复迹象。出于谨慎考虑，使用GitHub Enterprise Importer的迁移仍处于暂停状态。<br /><br />我们正在监控所有受影响服务的持续恢复情况，并将很快提供进一步更新。

原文System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly.

系统范围内的队列已清空，新任务正在按预期处理。针对自托管运行器未拾取任务的修复已全面部署。<br /><br />由Webhook触发的Actions工作流已恢复至全吞吐量。GitHub Pages、Copilot代码审查及Copilot编码代理均显示恢复迹象。使用GitHub Enterprise Importer的迁移仍暂停，作为预防措施。<br /><br />我们正在监控所有受影响服务的持续恢复情况，并将很快提供进一步更新。

原文<br />System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly.

我们已部署修复措施，解决运行器被分配无效作业的问题，并正在采取额外步骤清理受影响作业的积压。运行中工作流的作业完成率显著提升，成功率现已达到99%。托管运行器分配的全局队列几乎已清空，客户的并发队列正在处理中。另部署了一项变更，以加速处理作业请求的积压。 我们正逐步恢复webhook触发的Actions工作流的吞吐量，并监控系统稳定性。我们已为未拾取作业的自托管运行器部署修复，并正在逐步启用。 GitHub Pages、Copilot代码审查及Copilot编码代理可能仍会遭遇间歇性故障或延迟。使用GitHub Enterprise Importer的迁移仍处于暂停状态。 我们将继续监控所有受影响服务的恢复情况，并在条件改善时提供进一步更新。

原文We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.<br /><br />We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.<br /><br />GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.<br /><br />We continue to monitor recovery across all affected services and will provide another update as conditions improve.

我们正在继续解决影响GitHub Actions的问题。我们已经部署了一个修复程序，解决了运行器被分配已失效作业的问题，并且作业完成率正在改善。对于正在启动的工作流运行，成功率显著提升，目前达到97%。标准及大型运行器正在清空积压的队列工作。同时，一项变更正在进行中，以缓解现有自托管运行器未接收作业的问题。<br /><br />Webhook触发器仍处于限流状态以支持恢复。许多推送和拉取请求事件尚未触发新的工作流运行，我们正在努力安全地恢复全部吞吐量。<br /><br />GitHub Pages、Copilot代码审查和Copilot编码代理可能仍会遇到故障或延迟。使用GitHub Enterprise Importer的迁移仍处于暂停状态。<br /><br />我们将继续监控恢复情况，并在条件改善时提供进一步更新。

原文We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased significantly and are now at 97%. Standard and larger runners are now draining queued work. A change is also in progress to mitigate issues with existing self-hosted runners that are not picking up jobs.<br /><br />Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.<br /><br />GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.<br /><br />We are continuing to monitor recovery and will provide another update as conditions improve.

我们正在继续处理影响GitHub Actions的问题。为帮助恢复，Webhook触发器仍处于限流状态，因此许多推送和拉取请求事件未能触发新的工作流运行。<br /><br />我们已发现运行器被分配了不再有效的任务，并正在部署一项更改以解决此问题。GitHub托管和自托管运行器均受影响。<br /><br />Copilot代码审查、Copilot编码代理及GitHub Pages可能会遇到故障或延迟。使用GitHub Enterprise Importer的迁移已暂停，以支持缓解工作。

原文We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs.<br /><br />We identified runners being assigned jobs that are no longer valid and are deploying a change to address this issue. Both GitHub-hosted and self-hosted runners are affected.<br /><br />Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts.

我们正在继续处理影响GitHub Actions的问题。目前，Webhook触发器被限流以帮助恢复，我们正在处理约15%的Webhook，因此许多事件（如推送和拉取请求）未能触发工作流运行。在已排队的工作中，约有65%成功执行，相比事件初期低至30%至40%的成功率有所改善。<br /><br />我们已将剩余影响缩小到那些卡在重试不再可用作业的运行器上。GitHub托管和自托管运行器均受影响，我们正在努力恢复它们。<br /><br />Copilot代码审查、Copilot编码代理以及使用GitHub Enterprise Importer进行的迁移也可能受到影响。

原文We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs queued, approximately 65% are succeeding, improved from a low of 30 to 40% earlier in this incident.<br /><br />We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.<br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected.

我们正在继续处理影响GitHub Actions的问题。<br /><br />容量仍然受限，在逐步恢复期间，任务可能仍会延迟或失败。使用自托管运行器的客户在注册运行器时可能会遇到错误或速率限制。<br /><br />Copilot代码审查、Copilot编码代理以及使用GitHub Enterprise Importer进行的迁移也可能受到影响。Webhook投递可能会延迟。<br /><br />我们的工程师仍在积极处理中。

原文We are continuing to work on an issue affecting GitHub Actions. <br /><br />Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. Customers using self-hosted runners may see errors or rate limiting when runners register.  <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. <br /><br />Our engineers remain actively engaged.

我们正在继续处理影响多个GitHub服务的问题。<br /><br />工作流运行仍然失败，作业在开始前可能会长时间排队或超时。使用GitHub托管运行器的作业在容量受限时尤其受影响。<br /><br />使用自托管运行器的客户在运行器注册时可能会遇到错误或速率限制。<br /><br />Copilot代码审查、Copilot编码代理以及使用GitHub Enterprise Importer的迁移也可能受到影响。Webhook投递可能会延迟。<br /><br />恢复所需时间比我们预期的要长，工程师们仍在积极处理中。

原文We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. <br /><br />Recovery is taking longer than we expected, and engineers remain actively engaged.

我们正在继续处理影响多个GitHub服务的问题。<br /><br />工作流运行仍然失败或延迟启动，部分排队作业可能超时。<br /><br />使用自托管运行器的客户在注册运行器时可能会遇到错误或速率限制。<br /><br />Copilot代码审查、Copilot编码代理、托管运行器以及使用GitHub Enterprise Importer进行的迁移也可能受到影响。<br /><br />Webhook投递可能延迟。<br /><br />工程师已应用进一步缓解措施，并继续努力实现全面恢复。

原文We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected. <br /><br />Webhook deliveries may be delayed.<br /><br />Engineers have applied further mitigations and are continuing to work towards full recovery.

我们正在继续处理影响多个GitHub服务的问题。<br /><br />工作流运行可能失败或延迟启动，部分排队任务可能超时。<br /><br />Copilot代码审查、Copilot编码代理、托管运行器以及使用GitHub Enterprise Importer进行的迁移也可能受到影响。<br /><br />Webhook投递可能延迟。<br /><br />工程师已应用多项缓解措施，目前正在所有受影响的系统中推出进一步的修复方案。

原文We are continuing to work on an issue affecting multiple GitHub services.<br /><br />Workflow runs are failing or delayed in starting, and some queued jobs may time out. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected. <br /><br />Webhook deliveries may be delayed. <br /><br />Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.

我们正在继续处理影响GitHub Actions的问题。<br /><br />工作流运行仍然失败或延迟启动，部分排队作业可能超时。<br /><br />对Actions API的某些请求正在返回错误。使用GitHub Enterprise Importer进行迁移的客户可能会遇到失败。<br /><br />我们的工程师已应用多项缓解措施，目前正在推出进一步的修复。

原文We are continuing to work on the issue affecting GitHub Actions. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures. <br /><br />Our engineers have applied several mitigations and are rolling out a further fix now.

Actions 和 Pages 正经历可用性降级。我们正在继续调查。

原文Actions and Pages are experiencing degraded availability. We are continuing to investigate.

我们正在继续处理影响GitHub Actions的问题。<br /><br />部分工作流运行仍然延迟或无法完成，且对Actions API的一些请求正在返回错误。<br /><br />使用GitHub Enterprise Importer进行迁移的客户也可能遇到失败。<br /><br />工程师们正在积极努力，争取全面恢复。

原文We are continuing to work on the issue affecting GitHub Actions. <br /><br />Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors. <br /><br />Customers running migrations with GitHub Enterprise Importer may also see failures. <br /><br />Engineers are actively working towards full recovery.

Pages 正在经历性能降级。我们正在继续调查。

原文Pages is experiencing degraded performance. We are continuing to investigate.

Pages 运行正常。

原文Pages is operating normally.

Pages 正在经历性能降级。我们正在继续调查。

原文Pages is experiencing degraded performance. We are continuing to investigate.

我们正在调查影响GitHub Actions的错误。部分工作流运行无法启动或在执行过程中失败，且对Actions REST API的一些请求返回错误。<br /><br />部分客户可能还会在其工作流中遇到意外的速率限制。<br /><br />工程师已确定中断原因，并正在积极制定缓解措施。

原文We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors. <br /><br />Some customers may also see unexpected rate limiting in their workflows. <br /><br />Engineers have identified the source of the disruption and are actively working on a mitigation

Actions 正经历可用性降级。我们正在继续调查。

原文Actions is experiencing degraded availability. We are continuing to investigate.

我们正在调查有关Actions性能下降的报告。

原文We are investigating reports of degraded performance for Actions