Resolved incident
Incident with Copilot AI Model Providers
GitHub · Minor · Started
- Duration
- 41m
- Severity
- Minor
- Status
- Resolved
Summary
Minor · Resolved
On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.
Event timeline
How this incident unfolded, from the official status page.
Investigating
GitHub
We are investigating reports of degraded performance for Copilot AI Model Providers
Investigating
GitHub
We are seeing increased error rates from specific upstream AI Model Providers
Investigating
GitHub
We are experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Monitoring
GitHub
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Monitoring
GitHub
The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.
Resolved
GitHub
On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.