GitHub resolves disruption affecting some Copilot services

GitHub says an official service incident is resolved.

Oct 28, 2026
•
4 min read
Technobezz
GitHub resolves disruption affecting some Copilot services

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Updated 11:28 a.m. Eastern on October 28, 2026

GitHub says the incident affecting some Copilot services has been resolved, following degraded performance reported during the disruption.

What is affected

Degraded availability affected GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash in Copilot products and IDE surfaces.

Official update timeline

, marked Investigating

We are investigating reports of impacted performance for some GitHub services.

, marked Investigating

We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.

, marked Investigating

We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models 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 to continue using Copilot.

, marked Investigating

We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot.

, marked Investigating

We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.

, marked Investigating

Copilot is experiencing degraded performance. We are continuing to investigate.

, marked Monitoring

The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

, marked 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.

Read the official GitHub status page.

Track GitHub in the Technobezz status catalog.

Share