‹ 返回事件历史

使用WebHook、Pull请求和操作降级

原文Degradation with Webhooks, Pull Requests and Actions
已恢复较大故障GitHub
2026年6月26日星期五 01:50 ~ 2026年6月26日星期五 02:27(37 分钟)
受影响组件
Webhooks
Issues
Pull Requests
Actions
更新记录
已恢复2026年6月25日星期四 18:27

On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. <br /><br />The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07.

监控中2026年6月25日星期四 18:27

We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.

监控中2026年6月25日星期四 18:07

The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

排查中2026年6月25日星期四 17:58

服务目前性能下降。我们正在继续调查。

原文Issues is experiencing degraded performance. We are continuing to investigate.

排查中2026年6月25日星期四 17:53

Actions 正经历可用性降级。我们正在继续调查。

原文Actions is experiencing degraded availability. We are continuing to investigate.

排查中2026年6月25日星期四 17:50

We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

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

关于这些数据

事件从哪来?

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

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

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

持续时长怎么算?

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