Runner组和Runner相关权限页面中出现间歇性故障

2026年8月18日，在05:02 UTC至11:30 UTC期间，客户无法通过GitHub UI和API查看或管理Actions Runners及Runner Groups。<br /><br />该问题是由于后端请求读取runner和runner group数据时发生故障所致。故障源于该服务特有的一个已过期的认证证书。该证书已在KeyVault中轮换，但为避免此前由该操作引发的历史事件重演，启用其在运行时使用的步骤被暂停。<br /><br />通过在后端系统中完成新证书的启用，影响已得到缓解。我们已为此证书及其他证书增加了额外监控。该服务也正在作为我们可用性和规模工作的一部分被替换，以使此认证路径和秘密管理与所有GitHub服务的模式保持一致。

原文On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />The issue was caused by failures in backend requests 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 triggered by this operation. <br /><br />The impact was mitigated by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. This 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.

我们已实施缓解措施，并观察到恢复迹象。我们将持续监控恢复情况并更新进展。

原文We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.

我们已定位到Actions服务之间通信问题的根源，并正在着手缓解。使用Larger Runners的客户可能会遇到加载运行器组失败及运行器相关权限问题。

原文We have identified the source of a communication issue between Actions services and are working toward mitigation. Customers may experience failure to load runner groups and runner-related permissions issues when using Larger Runners.

我们正在调查关于使用较大运行器的客户无法加载运行器组及运行器相关权限的报告。

原文We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.

我们正在调查部分GitHub服务性能受影响的相关报告。

原文We are investigating reports of impacted performance for some GitHub services.