Actions 和 Pull Requests 相关事件
此事件已解决。感谢您在问题处理期间的耐心与理解。详细根本原因分析将在可用时尽快分享。
原文This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
影响Actions和Pull Requests的性能降级问题已得到缓解。我们正在监控以确保稳定性。
原文The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
我们已确认自UTC时间23:58起完全恢复。Actions工作流运行及拉取请求合并操作均正常。我们现在将解决该事件,同时继续监控服务健康状况。
原文We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.
我们已应用缓解措施,并观察到Actions工作流运行和受阻的拉取请求合并正在恢复。我们将继续监控合并提交创建的持续健康状况,然后再解决问题。
原文We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
我们正在调查影响由拉取请求事件触发的Actions工作流运行的高延迟和超时问题。20%的Actions运行启动延迟超过5分钟,且高达4%的运行未能触发。我们正在积极采取缓解措施,并将随着了解更多情况提供更新。
原文We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
我们正在调查有关Actions和Pull Requests性能下降的报告。
原文We are investigating reports of degraded performance for Actions and Pull Requests
关于这些数据
事件从哪来?
全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。