GitHub Status · History · Incident #6750

RESOLVED

Incident with Copilot AI Model Providers

Critical · Started Aug 27, 2026 · 10:04 AM

  • Duration

    2h 8m

  • Severity

    Critical

  • Detection lead

  • User reports

    Peak 1/hr

Summary

Incident with Copilot AI Model Providers

On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. <br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.


  • Started

    Aug 27, 2026 · 10:04 AM

  • Resolved

    Aug 27, 2026 · 12:12 PM

  • Duration

    2h 8m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    Aug 27 · 10:04 AM GitHub

    We are investigating reports of degraded availability for Copilot AI Model Providers

  • Investigating

    Aug 27 · 10:43 AM GitHub

    We are experiencing degraded availability for the Kimi K3 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.

  • Investigating

    Aug 27 · 11:58 AM GitHub

    Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.

  • Investigating

    Aug 27 · 12:12 PM GitHub

    The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces.<br />We will continue monitoring to ensure stability.

  • Resolved

    Aug 27 · 12:12 PM GitHub

    On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. <br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

User reports · incident window

Report volume over time

Hourly report count. Red bars mark the incident window.

Peak: 1 reports/hr

← Before incident After →

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.