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

推荐订阅源

Martin Fowler
Martin Fowler
有赞技术团队
有赞技术团队
博客园_首页
H
Help Net Security
GbyAI
GbyAI
aimingoo的专栏
aimingoo的专栏
V
Visual Studio Blog
The Cloudflare Blog
腾讯CDC
Jina AI
Jina AI
Last Week in AI
Last Week in AI
月光博客
月光博客
博客园 - 叶小钗
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
Blog — PlanetScale
Blog — PlanetScale
人人都是产品经理
人人都是产品经理
Engineering at Meta
Engineering at Meta
Y
Y Combinator Blog
Hugging Face - Blog
Hugging Face - Blog
博客园 - 聂微东
爱范儿
爱范儿
N
Netflix TechBlog - Medium
F
Fortinet All Blogs

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 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 Several GPT models degraded
Degraded Git Operations over SSH
2026-08-21 · via GitHub Status - Incident History

Resolved

On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for approximately four minutes. Git operations over HTTPS were not affected.

The incident was caused by a software defect in our load-balancing infrastructure that was triggered by a configuration change. The defect only occurred when connections passed through multiple layers of load balancers running the new configuration, which meant it was not detected during canary testing.

We mitigated the incident by rolling back the configuration change.

We are adding regression coverage for multi-layer load-balancer configurations and improving monitoring and alerting for Git operations over SSH to reduce our time to detection and mitigation of similar issues in the future.

Posted Aug 21, 2026 - 14:00 UTC