GitHub Copilot Kimi K3 Outage Resolved After Upstream Provider Issue

GitHub says Kimi K3 is available again in Copilot products and IDEs after an unnamed upstream provider issue. A detailed root-cause analysis is still pending.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Resolved service advisory • GitHub Copilot

GitHub says Kimi K3 is available again in Copilot products and IDE surfaces after an issue with an unnamed upstream model provider. GitHub marked the incident resolved at 8:12 a.m. EDT.[1]

Resolved at 8:12 a.m. EDT • August 27

Resolved. GitHub says the upstream-provider issue was mitigated, Kimi K3 became available again, and the Copilot AI Model Providers component returned to operational.[1][2]

The incident retains GitHub’s historical critical impact label, but that label describes the incident record—not the component’s current operational state.[1][2]

What GitHub confirmed

Affected model

Kimi K3 in Copilot products and IDE surfaces.[1]

Vendor attribution

An issue with an upstream model provider. GitHub has not named that provider.[1]

During the incident

GitHub recommended another available model or Auto while Kimi K3 was degraded.[1]

Still unknown

GitHub has not yet published the provider identity, detailed root cause, affected-user share, regions or error rate; it says a detailed analysis will follow.[1]

What to do if Kimi K3 still fails

  1. Check GitHub’s live status first. GitHub has resolved this incident, so confirm there is not a new disruption before changing local settings.[1]
  2. Retry once, then isolate. If Kimi K3 still fails while GitHub remains operational, compare another model or Auto before deeper local troubleshooting.[1]
  3. Preserve unsaved work. Avoid repeated automated retries that could duplicate requests or create confusion while you isolate a continuing failure.[1]
  4. Keep changes reversible. If another model works, that supports pausing invasive local changes while you verify Kimi K3, IDE and extension state.[1]
Important boundary

GitHub has not identified a cyberattack, breach, data compromise or malicious actor in this incident. It also has not linked the disruption to repositories, Git operations, Actions, Packages or billing.[1][2]

Timeline

  • 6:04 a.m. EDT: GitHub opened an investigation into degraded availability for Copilot AI Model Providers.[1]
  • 6:43 a.m. EDT: GitHub named Kimi K3, described the upstream-provider issue and published the model-switching workaround.[1]
  • 7:58 a.m. EDT: GitHub reported that the component was experiencing degraded performance and continued investigating; the component state changed from major outage to degraded performance.[1][2]
  • 8:12 a.m. EDT: GitHub said the upstream issue was mitigated and Kimi K3 was available again, then marked the incident resolved and returned the component to operational.[1][2]

Bottom line

Kimi K3 is available again according to GitHub. If problems continue while the status page remains operational, compare another model or Auto, preserve your work and then proceed with normal local troubleshooting. Keep the attribution narrow: GitHub has not named the upstream provider or published the detailed root cause.[1]

Sources

  1. GitHub Status — incidents API (incident tx9qn4khd664, accessed August 27, 2026)
  2. GitHub Status — components API (Copilot AI Model Providers component, accessed August 27, 2026)
  3. GitHub Status — public incident page

Reporting cutoff: August 27, 2026, 8:13 a.m. EDT / 12:13 UTC. Status can change after publication; use GitHub’s incident page for the newest update.