某些副驾驶云代理作业未启动
2026年8月5日，世界协调时间11:02至11:54期间，GitHub Copilot云代理服务出现降级，新的云代理任务启动被延迟。在此期间，100%的新提交代理任务受到影响。此次事件仅限于云代理任务的延迟，没有任务丢失，积压队列已于世界协调时间13:00处理完毕。原因是一个用于保护服务可用性的内部速率限制被启用得比预期更广泛，导致延迟的流量超出预期。<br /> <br />当速率限制窗口过期后，服务恢复正常。随后，我们调整了该控制措施，使其不再影响无关的编码代理流量。<br /> <br />我们正在努力改进该控制措施的范围界定以及我们的监控和警报系统，以减少未来类似问题的检测和缓解时间。
原文On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected. <br /> <br />The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. <br /> <br />We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Copilot云代理任务已恢复，延迟任务的积压正在处理中。
原文Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
故障已缓解。我们正在监控以确保稳定性。
原文The degradation has been mitigated. We are monitoring to ensure stability.
我们正在调查部分GitHub服务性能受影响的相关报告。
原文We are investigating reports of impacted performance for some GitHub services.
关于这些数据
事件从哪来？
全部来自各厂商官方状态页的公开接口，由本站每 5 分钟同步一次，保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文，本站不做改写；点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史？
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商（多数国产大模型属于此类）无法取得可信数据，本站不做自建拨测去猜，因此也不会出现在状态总览里。
持续时长怎么算？
按官方标注的开始时间到恢复时间计算；尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。