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

推荐订阅源

D
Docker
B
Blog RSS Feed
Microsoft Security Blog
Microsoft Security Blog
Y
Y Combinator Blog
N
Netflix TechBlog - Medium
M
MIT News - Artificial intelligence
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
C
Check Point Blog
The GitHub Blog
The GitHub Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
P
Proofpoint News Feed
Martin Fowler
Martin Fowler
大猫的无限游戏
大猫的无限游戏
GbyAI
GbyAI
博客园_首页
A
About on SuperTechFans
Blog — PlanetScale
Blog — PlanetScale
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
T
The Blog of Author Tim Ferriss
The Cloudflare Blog

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