GitHub Copilot reported this minor-impact incident on its official status page on Jul 29, 2026, 20:07 UTC. It was resolved after 1h 44m.
Right now GitHub Copilot is operational. Live GitHub Copilot status →
On July 29, 2026, between 19:45 UTC and 21:51 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.006%, while failures for Fable 5 peaked at 21%. 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.
The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered.
The external AI model provider is continuing to investigate.
The external AI model provider has identified the issue and is working to resolve.
We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features.
We are seeing increased error rates with requests to specific model providers.
We are investigating reports of degraded performance for Copilot AI Model Providers
Our 5-minute checks didn't record a change in GitHub Copilot's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
GitHub Copilot reported 15 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 14m. See GitHub Copilot's uptime and incident history