惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

aimingoo的专栏
aimingoo的专栏
宝玉的分享
宝玉的分享
J
Java Code Geeks
Martin Fowler
Martin Fowler
博客园 - Franky
I
InfoQ
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
S
SegmentFault 最新的问题
B
Blog
The Cloudflare Blog
F
Fortinet All Blogs
量子位
腾讯CDC
博客园 - 司徒正美
D
Docker
大猫的无限游戏
大猫的无限游戏
Microsoft Azure Blog
Microsoft Azure Blog
T
The Blog of Author Tim Ferriss
V
Visual Studio Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
D
DataBreaches.Net
小众软件
小众软件

GitHub Status - Incident History

Incident with Actions and Pull Requests Disruption with GitHub Billing Disruption with some GitHub services Actions delays in starting runs Elevated errors on Fable 5 due to upstream provider Degraded Git Operations over SSH Intermittent failures creating agent tasks Incident with Actions Intermittent failures in runner group and runner-related permissions pages Incident with GitHub.com Disruption with GHEC Team Sync Errors with the Fable 5 Model in Copilot Incident with Webhooks Disruption with Login and Release Asset downloads Incident with Pull Requests and Issues Incident with GraphQL API Requests Disruption with Copilot for access to some models Disruption with creation of fine grained personal access tokens Incident with Pages - Deployment Lag Incident with Actions Some Copilot Cloud Agent jobs not starting Incident with Copilot Incident with Copilot AI Model Providers Degraded availability GPT 5.6 Luna Copilot model Claude Fable 5 experiencing elevated errors Incident with Copilot AI Model Providers Incident with Actions Test Incident Posted in Error – No Customer Impact (Will Be Removed) Incident with GraphQL API Requests Actions run failures and delays
Elevated rate of Git push errors
2026-05-25 · via GitHub Status - Incident History

Resolved

On May 25, 2026, between 09:02 UTC and 09:11 UTC, Git push operations over HTTPS and SSH experienced elevated failures. During this window, an average of 31% and a peak of 43% of push requests failed.

The incident was caused by a recently enabled code path that issued an unexpectedly expensive database query against a primary database. The resulting load exhausted the database's connection pool, which caused the push failures above. The acute impact resolved automatically as in-flight work completed. We mitigated the incident by disabling the feature flag controlling the new code path. To prevent recurrence, we have updated the affected background workflows to route reads to replica databases instead of the primary, removing the specific code pattern that caused this incident; broader follow-up work is underway to apply the same safeguard to similar workflows across GitHub.

Posted May 25, 2026 - 09:02 UTC