带有行动的事件
2026年10月22日协调世界时13:05至15:20,我们的事件流平台出现降级,导致作业处理延迟峰值升高19-35秒,作业处理时间延长至4分钟——这进而造成Actions工作流和步骤结果延迟(最长13分钟)、通知延迟(20分钟)以及仓库推送事件延迟(12分钟)。仓库服务于14:32开始恢复,Actions服务于14:59开始恢复。该问题在16:26再次发生,再次影响Actions运行、仓库推送事件和通知。恢复工作于17:16开始,并于2:07完成。<br /><br />此次事故是由一次部署期间负载显著增加,加之客户端连接风暴,导致我们的Kafka事件流代理过载所致。<br /><br />为防止未来再次发生,我们已扩展受影响的集群,将流量转移至负载较低的集群,并实现了可调的客户端重连退避机制。
原文On October 22, 2026, from 13:05 to 15:20 UTC, our event streaming platform was degraded resulting in elevated job processing latency spikes of 19-35 seconds and elevated job processing times of 4m – this resulted in delayed Actions workflow and step results (up to 13m), notifications (20m) and repository push events (12m). Recovery for repositories began at 14:32, with Actions recovery beginning at 14:59. The issue reoccurred at 16:26 again impacting Actions runs, repo push events, and notifications. Recovery began at 17:16 and completed at 2:07. <br /><br />The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. <br /><br />To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff.
GitHub Actions 工作流和步骤结果处理已恢复。仓库更新处理也已恢复正常。
原文GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.
影响Actions的服务降级问题已得到缓解。我们正在监控以确保稳定性。
原文The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
我们正在看到恢复,仓库更新处理已恢复正常。影响GitHub Actions工作流和步骤结果的延迟随着我们扩大处理能力正在继续清除;剩余积压预计需要约20分钟来消化。
原文We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
仓库更新处理已恢复。我们正在继续处理影响 GitHub Actions 工作流和步骤结果的延迟问题。随着进展,我们将分享更多更新。
原文Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
我们正在调查处理GitHub Actions工作流和步骤结果以及部分仓库更新时的延迟问题。
原文We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
我们正在调查有关Actions性能下降的报告。
原文We are investigating reports of degraded performance for Actions
关于这些数据
GitHub的故障事件数据从哪来?
全部来自GitHub 官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
顶部的组件状态条怎么看?
每一格是一天,绿色表示GitHub 官方状态页当天未记录异常,黄色表示部分降级,红色表示当天有较大故障,灰色表示该组件当时还没有数据。右侧的可用率是官方口径的 90 天统计,与状态总览页显示的是同一份数据。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。
完整的服务清单与实时状态见状态总览。