‹ 返回事件历史

WebHooks事件

原文Incident with Webhooks
已恢复轻微故障GitHub
2026年7月15日星期三 01:38 ~ 2026年7月15日星期三 02:01(23 分钟)
受影响组件
Webhooks
更新记录
已恢复2026年7月14日星期二 18:01

2026年7月14日,在15:17至15:37 UTC期间,对GitHub内部webhook投递管道的一次发布导致一部分webhook投递记录在处理并成功投递后,未能写入我们的webhook投递存储中。受影响的投递记录将从webhook投递界面和API中缺失,并且无法用于重新投递。 根本原因是一次不协调的发布:管道组件之间投递记录交接方式的变更,在生成这些记录的上游组件尚未更新以匹配之前就被部署了。在发布进行期间,受影响的记录被静默跳过而非持久化,且没有自动重试。影响在发布完成后立即结束。 大约有240万条投递记录被跳过(约占20分钟影响窗口的4%,占典型24小时周期的0.04%)。重要的是,这些被跳过的投递中有95%成功到达了客户端点,只是投递记录缺失。在约5%未能到达客户端点的情况下,只有约1.4%(5,463条)对应在过去28天内重试过投递的webhook。 为防止再次发生,我们正在改进对不安全模式变更的自动检测,并加强涉及管道中多个组件变更的发布协调。

原文On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery. The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in progress, affected records were silently skipped rather than persisted, with no automatic retry. The impact ended as soon as the rollout was completed. About 2.4M delivery records were skipped (approximately 4% of the 20-minute impact window, 0.04% of a typical 24-hour period). Importantly, 95% of these skipped deliveries reached customer endpoints successfully, only the record of the delivery is missing. Of the ~5% that failed to reach customer endpoints, only ~1.4% (5,463) map to webhooks that retried their deliveries in the past 28 days. To prevent recurrence, we are improving our automated detection of unsafe schema changes and tightening rollout coordination for changes that span multiple components in the pipeline.

监控中2026年7月14日星期二 17:55

影响Webhooks的性能降级问题已得到缓解。我们正在持续监控以确保稳定性。

原文The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.

排查中2026年7月14日星期二 17:55

在UTC时间15:17至15:27之间,一次进行中的部署产生了意外副作用,导致在某些情况下,即使webhook投递已被接受并处理,其投递状态也未能全部持久化。客户可能会在UI中注意到webhook投递缺失,且这些投递将无法重试。<br /><br />部署完成后,影响已自动解除。

原文Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable.<br /><br />Impact resolved automatically once the deployment completed.

排查中2026年7月14日星期二 17:38

我们正在调查有关Webhooks性能下降的报告。

原文We are investigating reports of degraded performance for Webhooks

事件内容来自 GitHub 官方状态页:查看官方原文。中文由 AI 翻译,仅供快速理解,以官方英文原文为准。

关于这些数据

事件从哪来?

全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。

为什么有的服务查不到历史?

本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。

持续时长怎么算?

按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。