GitHub resolved the Kimi K3 model outage in Copilot caused by an issue at the provider
On 27 August 2026, GitHub addressed degraded availability of the Kimi K3 model in Copilot and IDE extensions, caused by an issue at the upstream model provider. The incident lasted roughly two hours and was resolved.
GitHub reported degraded availability of the Copilot AI Model Providers service on 27 August 2026 and began investigating. At 10:43 UTC, it clarified that the issue specifically affected the Kimi K3 model in Copilot and IDE extensions and was caused by a problem at an external (upstream) model provider. The company recommended that users select another model or “Auto” mode during the outage so they could continue using Copilot without interruption.
At 11:58 UTC, GitHub confirmed that the Copilot AI Model Providers service continued to experience degraded performance and that the investigation was ongoing.
At 12:12 UTC, the company announced that the issue at the upstream provider had been mitigated and that the Kimi K3 model was available again in Copilot products and IDE extensions, adding that it would continue to monitor service stability. Shortly afterward, the incident was marked as resolved. According to the company, a detailed root cause analysis is to be published once it is available.
Why it matters
Developers specifically using the Kimi K3 model in Copilot experienced limited or unavailable functionality for this model in both Copilot and IDE extensions during the incident; the company recommended temporarily switching to another model or “Auto” mode so they could continue working without interruption. The incident also shows that the availability of specific models in Copilot depends on external (upstream) providers, so an outage on their side can affect the end-user service even beyond the direct control of GitHub.
Two audiences, two different impacts
What this means
For individuals
Anyone who regularly uses the Kimi K3 model in Copilot may have encountered unavailability or slower responses during the incident; the solution was to temporarily switch to another model or “Auto” mode.
For a business
The incident highlights the dependence of GitHub Copilot on external model providers, whose outages can temporarily limit the availability of a specific model in enterprise developer tools, although in this case the issue was resolved in roughly two hours.
ProductivityCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.