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

推荐订阅源

N
Netflix TechBlog - Medium
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
爱范儿
爱范儿
博客园_首页
雷峰网
雷峰网
Hugging Face - Blog
Hugging Face - Blog
V
Visual Studio Blog
The Cloudflare Blog
罗磊的独立博客
美团技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
大猫的无限游戏
大猫的无限游戏
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
博客园 - 叶小钗
The GitHub Blog
The GitHub Blog
Last Week in AI
Last Week in AI
J
Java Code Geeks
MyScale Blog
MyScale Blog
G
Google Developers Blog
U
Unit 42
Y
Y Combinator Blog
P
Proofpoint News Feed
Vercel News
Vercel News

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
Incident with Copilot
2026-05-19 · via GitHub Status - Incident History

Resolved

On May 19, 2026, between 05:30 UTC and 14:50 UTC, some Copilot users experienced failures when using code completions, chat sessions, and cloud agent sessions. At peak impact, approximately 13% of Copilot API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC.

The incident was caused by rate limits being exceeded on a shared infrastructure component. A recently enabled feature increased call volume to this component, and the combined load exceeded capacity limits as traffic increased during business hours.

We mitigated the incident by deploying a caching layer to reduce load on shared infrastructure. To prevent recurrence, we are separating rate limit scopes between services, adding monitoring for internal dependency rate limiting, and reducing redundant calls.

Posted May 19, 2026 - 05:30 UTC