Incident with Copilot AI Model Providers

criticalGitHubCopilotAug 27, 2026 10:04Duration: 2h 8m
api
API Issue

Summary

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.

Impact

critical

Timeline

Aug 27, 2026 10:04

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

via statuspage
+38m
Aug 27, 2026 10:43

[investigating] 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.

via statuspage
+1h 15m
Aug 27, 2026 11:58

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

via statuspage
+15m
Aug 27, 2026 12:12

[investigating] 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.

via statuspage
+0m
Aug 27, 2026 12:12

[resolved] This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

via statuspage
+0m
Aug 27, 2026 12:12

[resolved] 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.

via statuspage

Lessons Learned

GitHub has experienced 148 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to api have occurred 959 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: API Issue. Consider implementing preventive measures specific to this failure category.