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

推荐订阅源

有赞技术团队
有赞技术团队
G
Google Developers Blog
T
Tailwind CSS Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
J
Java Code Geeks
P
Proofpoint News Feed
V
Visual Studio Blog
爱范儿
爱范儿
The Cloudflare Blog
博客园 - 叶小钗
V
V2EX
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
M
MIT News - Artificial intelligence
Microsoft Security Blog
Microsoft Security Blog
博客园 - 聂微东
H
Help Net Security
B
Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 【当耐特】
量子位
宝玉的分享
宝玉的分享
WordPress大学
WordPress大学
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知

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
[Retroactive] Incident with GitHub.com
2026-05-15 · via GitHub Status - Incident History

Resolved

Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed.

The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.

Posted May 15, 2026 - 02:30 UTC