Skip to content
context Other

Brief outage of the Fable 5 model in GitHub Copilot due to an issue at the model provider

clearly official source

On 1 August, GitHub reported elevated error rates and degraded availability of the Fable 5 model in Copilot products and IDE editors due to an issue at the upstream model provider. The incident lasted from 18:03 to 18:44 UTC and was resolved.

According to the GitHub Status page, GitHub reported on 1 August 2026 at 18:03 UTC that it was investigating elevated error rates for “Copilot AI Model Providers”, specifically elevated error rates from certain upstream AI model providers. At 18:20 UTC, the company clarified that the issue involved degraded availability of the Fable 5 model in Copilot products and IDE editors, caused by an issue at the upstream model provider. The company recommended that users select another model or the “Auto” option while the fix was underway so they could continue using Copilot.

At the same time (18:20 UTC), the company announced that it had mitigated the degradation and was continuing to monitor service stability. At 18:23 UTC, it confirmed that the issue at the upstream model provider had been resolved and Fable 5 was available again in Copilot products and IDE editors. The incident was formally closed at 18:44 UTC, with GitHub stating that it would publish a detailed root cause analysis later.

The entire incident lasted approximately 41 minutes. The source does not state how many users were affected or the exact cause of the issue at the upstream model provider.

What changed

Why it matters

For developers actively using the Fable 5 model in GitHub Copilot, the incident meant temporary unavailability or errors during code completion and chat for just under an hour, with switching to another model or “Auto” mode as the recommended workaround. For companies running Copilot as part of their development workflow, this illustrates the dependence on upstream model providers — a brief outage at a third party immediately affects tool availability, even though the GitHub infrastructure itself was not compromised.

Two audiences, two different impacts

What this means

01

For individuals

GitHub Copilot users who had selected the Fable 5 model may have encountered errors or unavailability on 1 August between 18:03 and 18:44 UTC; as a workaround, GitHub recommended switching to another model or “Auto” mode.

What to do If you use GitHub Copilot with the Fable 5 model and encounter errors, try switching to another model or “Auto” mode.
More practical updates →
02

For a business

Companies relying on GitHub Copilot with the Fable 5 model faced a brief availability outage due to an issue at the upstream model provider; the incident was resolved within 41 minutes, with no reported impact on data or permanent loss of functionality.

Productivity
What to decide Follow the planned investigation into the cause (root cause analysis) by GitHub if the team repeatedly encounters outages affecting a specific model in Copilot.
More business impacts →
AI Copilot availability Fable 5 GitHub incident model outage

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
GitHub Status — incident history official service status · first detected Incident with Copilot AI Model Providers