GitHub reports disruption with some services

GitHub says an official service incident is resolved.

Sep 15, 2026
•
3 min read
Technobezz
GitHub reports disruption with some services

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Updated 7:17 a.m. Eastern on September 15, 2026

GitHub says the incident affecting some GitHub services is resolved, with the final update stating the incident has been resolved.

What is affected

The incident involved Copilot AI Model Providers, with degraded availability for Claude Fable 5.1 affecting some Copilot products and integrated development environments.

Official update timeline

, marked Investigating

We are investigating reports of impacted performance for some GitHub services.

, marked Monitoring

We are investigating degraded availability for Claude Fable 5.1, affecting some Copilot products and integrated development environments. The issue is caused by a problem with our upstream model provider. Customers can use another model or select Auto while we investigate.

, marked Investigating

Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.

, marked Investigating

We continue to investigate intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customers can use another model or select Auto while we monitor the situation.

, marked Investigating

We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers can select another model or Auto in the meantime.

, marked Investigating

The issues with our upstream model provider have been resolved, and Claude Fable 5.1 is once again available in Copilot products and IDE surfaces.

We will continue monitoring to ensure stability, but mitigation is complete.

, marked Resolved

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the official GitHub status page.

Track GitHub in the Technobezz status catalog.

Share