WebHooks事件
2026年8月13日14:24至14:53 UTC期间,一个例行的后台任务在删除某个组织时压垮了一个关键共享数据库,导致多个GitHub服务短暂出现错误率上升和响应变慢。受影响最严重的是webhook管理API,对Git操作、拉取请求、问题、软件包、登录和Copilot的影响较小。该任务完成后,影响在约14:53 UTC自行消除;我们在15:36 UTC解决了此事件。<br /><br />受影响的用户可能会遇到错误率短暂增加和响应变慢的情况,主要是在创建、列出或更新webhook时,对拉取请求、问题、软件包和Git操作的影响较小。故障在约14:37 UTC达到峰值,持续几分钟,错误率约为1%。<br /><br />为防止未来发生类似事件,我们已部署了一项更新,启用了更安全的组织删除路径,并对数据库上的删除保留设置了上限。基于这些更改,我们正在审计所有写入共享数据库的批量删除和清理任务,以避免未来出现类似问题。
原文Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. <br /><br />Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. <br /><br />To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.
我们已暂时禁用了导致影响的后台任务。目前影响已完全消除。
原文We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.
影响Git操作、Issues、Packages、Pull Requests和Webhooks的性能降级问题已得到缓解。我们正在监控以确保稳定性。
原文The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
我们目前正在调查14:32至14:46 UTC期间Git操作(特别是推送)、问题、拉取请求、包注册表和webhooks服务出现的短暂降级问题。我们已经确定了降级的根源,并正在研究缓解策略以防止再次发生。
原文We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.
Packages 目前性能下降。我们正在继续调查。
原文Packages is experiencing degraded performance. We are continuing to investigate.
Git Operations 正在经历性能下降。我们正在继续调查。
原文Git Operations is experiencing degraded performance. We are continuing to investigate.
服务目前性能下降。我们正在继续调查。
原文Issues is experiencing degraded performance. We are continuing to investigate.
Pull Requests 正经历性能下降。我们正在继续调查。
原文Pull Requests is experiencing degraded performance. We are continuing to investigate.
我们正在调查有关Webhooks性能下降的报告。
原文We are investigating reports of degraded performance for Webhooks
关于这些数据
GitHub的故障事件数据从哪来?
全部来自GitHub 官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
顶部的组件状态条怎么看?
每一格是一天,绿色表示GitHub 官方状态页当天未记录异常,黄色表示部分降级,红色表示当天有较大故障,灰色表示该组件当时还没有数据。右侧的可用率是官方口径的 90 天统计,与状态总览页显示的是同一份数据。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。
完整的服务清单与实时状态见状态总览。