带有行动的事件
2026年7月29日，从14:51 UTC到15:28 UTC，GitHub Actions经历了REST API请求超时和错误增多、运行器注册失败，以及对于流量由单一基础设施站点服务的客户，工作流启动延迟的问题。这是由该站点内部一个配置不足的Actions服务引起的：在负载增加时，其实例内存耗尽并变得无响应，由于Actions API请求同步等待该服务，通过受影响站点路由的请求停滞并超时。事件期间，大约2%的工作流被延迟。由其他站点服务的请求未受影响。通过受影响站点路由的标准和大型托管运行器都可能遇到作业启动延迟。<br /><br />通过扩展受影响站点中的运行器管理服务并增加副本数量，问题得到缓解，API可用性恢复，工作流启动恢复正常。我们正在努力为该服务添加水平自动扩展、内存饱和警报和扩展预测监控，以及响应者操作手册，以降低未来发生类似问题的可能性。
原文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.
影响Actions的服务降级问题已得到缓解。我们正在监控以确保稳定性。
原文The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
我们正在调查一个影响GitHub Actions的问题。部分客户可能会遇到运行器注册超时或失败的情况，工作流运行在启动时也可能出现延迟。我们的团队正积极通过扩展额外基础设施的容量来减轻影响。
原文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.
我们正在调查有关Actions可用性下降的报告。
原文We are investigating reports of degraded availability for Actions
关于这些数据
事件从哪来？
全部来自各厂商官方状态页的公开接口，由本站每 5 分钟同步一次，保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文，本站不做改写；点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史？
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商（多数国产大模型属于此类）无法取得可信数据，本站不做自建拨测去猜，因此也不会出现在状态总览里。
持续时长怎么算？
按官方标注的开始时间到恢复时间计算；尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。