GitHub Actions、GitHub Pages 和 Webhooks 的可用性下降

2026年10月19日协调世界时15：24至16：52期间，GitHub Actions、GitHub Pages以及由Actions生成的webhook出现服务降级。GitHub.com上的实时更新和代码搜索在此期间的部分时段也出现降级。未发生数据丢失。<br /><br />影响<br /><br />- 工作流状态更新、日志和检查出现延迟。<br />- GitHub托管运行器上5.13%的作业启动延迟，0.02%的工作流运行失败。<br />- 在最初30分钟内，对Actions作业REST API的请求中有8.47%返回错误。<br /><br />Pages部署和由Actions运行生成的webhook出现延迟。<br /><br />一个用于存储日志和运行状态的内部Actions服务在一个云区域中失去了与部分缓存服务器的连接，并立即同时从每台服务器重试连接。由此产生的新连接激增使我们数据中心与该区域之间的共享网络链路过载，这也干扰了使用同一链路的其他服务。我们通过将Actions服务从受影响的缓存服务器上移开并减少该链路上其他服务的连接来缓解该事件。随后我们处理了延迟的Actions工作。我们正在继续调查初始连接超时的原因。<br /><br />我们当时已经在推出对该服务打开新连接速度的限制，但在事件发生时该限制仍处于影子模式（仅记录日志，未强制执行）。此后我们已全面强制执行该限制，并限制了该服务的并发连接尝试次数。我们正在将这些限制扩展到其他Actions服务，为重试添加退避机制，限制单个服务可使用的共享网络容量，并改进告警以便更快找到连接激增的来源。

原文On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. <br /><br />Impact <br /><br /> - Workflow status updates, logs, and checks were delayed. <br /> - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. <br /> - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. <br /><br />Pages deployments and webhooks generated by Actions runs were delayed. <br /><br />An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. <br /><br />We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster.

Actions、Pages 和 Webhooks 均正常运行。

原文Actions, Pages and Webhooks are operating normally.

在采取缓解措施后，我们看到了恢复的迹象，并正在继续监控。<br /><br />客户可能仍会遇到 GitHub Actions 工作流状态更新、GitHub Pages 部署以及由 Actions 运行生成的检查和 webhook 事件出现延迟的情况。

原文We’re seeing recovery following mitigation and are continuing to monitor. <br /><br />Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.

我们目前正在调查影响 GitHub Actions、GitHub Pages 和 Webhooks 的可用性下降问题。<br /><br />客户可能会遇到工作流处理、站点构建和 webhook 交付延迟的情况。<br />

原文We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. <br /><br />Customers may experience delays in workflow processing, site builds and webhook delivery.<br />

Webhooks 目前性能下降。我们正在继续调查。

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

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

原文We are investigating reports of degraded performance for Actions and Pages