GitHub的一些服务中断
从2026年6月26日23:40 UTC至2026年6月28日20:55 UTC,Copilot Cloud Agent出现性能降级。代理在报告进度、回复拉取请求评论或打开拉取请求时可能失败。受影响的内置工具调用平均错误率约为8%,每小时错误率峰值约为26%。<br /><br />此问题源于Copilot Cloud Agent运行时部署期间引入的一个回归,导致多个内置代理工具不可用。在许多情况下,受影响的工具调用静默失败,因此代理任务看似成功。这一监控缺口意味着识别故障所需的时间比预期更长。我们通过将运行时部署回滚到先前稳定版本来缓解此事件。<br /><br />我们已为此类工具可用性错误添加了监控和警报,以缩短检测时间。同时,我们正在为这些内置代理工具添加回归测试,并改进未来运行时推出的发布安全性,以避免类似问题。
原文From June 26, 2026 at 23:40 UTC through June 28, 2026 at 20:55 UTC, Copilot Cloud Agent was degraded. The agent could fail when reporting progress, replying to pull request comments, or opening pull requests. For affected built-in tool calls, the average error rate was approximately 8%, with hourly error rates peaking around 26%.<br /><br />This was due to a regression introduced during a Copilot Cloud Agent runtime deployment that caused several built-in agent tools to become unavailable. In many cases, the affected tool calls failed silently so agent jobs appeared to succeed. This monitoring gap meant it took longer than expected to identify the failure. We mitigated the incident by reverting the runtime deployment to the previously stable version.<br /><br />We've added monitoring and alerting for this class of tool-availability error to reduce time-to-detection. We're also adding regression tests for these built-in agent tools, and improving the shipping safety for future runtime rollouts to avoid similar issues.
Copilot云代理在打开拉取请求、推送更改和回复评论时一直遇到间歇性问题。修复程序已部署,我们正在验证该修复。
原文Copilot cloud agent had been experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. A fix has been deployed and we are validating that fix.
Copilot 云代理在打开拉取请求、推送更改和回复评论时遇到间歇性问题。我们已验证修复方案,目前正在部署该修复。
原文Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have validated a fix and are deploying that fix now.
Copilot云代理在打开拉取请求、推送更改和回复评论时遇到间歇性问题。我们已定位问题,正在验证修复方案。
原文Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have identified the issue and are validating a fix.
我们正在调查部分GitHub服务性能受影响的相关报告。
原文We are investigating reports of impacted performance for some GitHub services.
关于这些数据
事件从哪来?
全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。