‹ 返回事件历史

延迟启动操作运行

原文Delays starting Actions runs
已恢复严重故障GitHub
2026年7月9日星期四 12:34 ~ 2026年7月9日星期四 21:52(9 小时 17 分钟)
受影响组件
Actions
Pages
更新记录
已恢复2026年7月9日星期四 13:52

2026年7月9日,UTC时间03:29至13:39期间,GitHub Actions在GitHub托管的运行器上遇到了作业启动延迟和失败的问题。该事件由负责配置托管运行器的后端数据服务处于不健康状态引起,导致部分工作负载无法获取运行器。在事件的大部分时间里,托管运行器上约有8%的工作流运行延迟超过5分钟,而约2%未能启动。<br /><br />在13:39 UTC,我们恢复了后端数据复制系统的健康状态,使配置得以恢复,累积的工作流积压得以清空。随后服务性能恢复到预期水平。我们正在提升配置服务的弹性、工作负载分布和容量平衡,以减少类似事件发生的可能性和影响。

原文On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start.<br /><br />At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.

监控中2026年7月9日星期四 13:41

Actions、Pages builds、Copilot Cloud Agent和Copilot Code review均已恢复并得到缓解。<br /><br />我们正在持续监控以确保完全恢复,并调查受影响基础设施的健康状况。

原文Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated.<br /><br />We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.

监控中2026年7月9日星期四 13:39

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

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

排查中2026年7月9日星期四 13:17

我们正在持续监控Actions和Pages构建的缓慢恢复情况,系统正在处理大量积压任务。<br /><br />在系统恢复期间,客户可能会看到少量API和作业失败。<br /><br />在此事件期间,Copilot Cloud Agent和Copilot Code Review也未能启动约30分钟,我们正在监控恢复情况。<br /><br />整个事件期间,Pages始终可访问。

原文We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog.<br /><br />Customers may see a small rate of  API and job failures as the system is recovering.<br /><br />Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.<br /><br />Pages were accessible throughout the incident.

排查中2026年7月9日星期四 13:16

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

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

排查中2026年7月9日星期四 12:54

我们正在观察Actions和Pages的恢复情况。<br /><br />在约20分钟的时间段内,约96%的GitHub Actions在GitHub托管的运行器上无法启动,但现已恢复,我们正在看到任务正在处理中。<br /><br />在此期间,GitHub Pages构建也出现失败,但Pages仍然可以访问。<br /><br />我们将继续监控,确保完全恢复。

原文We're seeing Actions and Pages recovery. <br /><br />For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.<br /><br />GitHub pages builds were also failing during that period, but Pages are still accessible.<br /><br />We are continuing to monitor for full recovery.

排查中2026年7月9日星期四 12:46

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

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

排查中2026年7月9日星期四 12:36

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

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

排查中2026年7月9日星期四 12:01

大约30%的GitHub Actions在GitHub托管运行器上的运行遭遇启动延迟超过5分钟的情况。其中一小部分已耗尽重试次数,未能启动。<br />这已导致部分客户超出其托管计算并发限制,并受到更严重的影响。<br /><br />我们正在继续实施基础设施缓解措施。<br /><br />下一更新将在一小时后发布。

原文Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.<br />This has caused some customers to exceed their hosted compute concurrency and experience increased impact.<br /><br />We are continuing to working on infrastructure mitigations. <br /><br />Next update in one hour.

排查中2026年7月9日星期四 10:15

大约30%的GitHub Actions在GitHub托管的运行器上执行时,启动延迟超过5分钟。其中一小部分因重试耗尽而无法启动。

原文Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.

排查中2026年7月9日星期四 10:07

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

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

排查中2026年7月9日星期四 06:01

我们正在继续制定缓解措施。

原文We are continuing to work on a mitigation.

排查中2026年7月9日星期四 04:51

约5%在GitHub托管运行器上的GitHub Actions运行正经历超过5分钟的启动延迟。其中一小部分运行在长时间延迟后可能会失败。我们已确定原因,并正在制定缓解措施。

原文Approximately 5% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.

排查中2026年7月9日星期四 04:34

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

原文We are investigating reports of degraded performance for Actions

事件内容来自 GitHub 官方状态页:查看官方原文。中文由 AI 翻译,仅供快速理解,以官方英文原文为准。

关于这些数据

事件从哪来?

全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。

为什么有的服务查不到历史?

本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。

持续时长怎么算?

按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。