GitHub Copilot outage on Oct 28, 2026: disruption with some Copilot services

Reports during the incident

Every 15 minutes, 13:00 UTC to 16:30 UTC. Grey: normal. Red line: official incident.

13:00 UTC14:12 UTC15:28 UTC16:30 UTC

What people reported

0 reports during the incident

No reports in this window.

GitHub's updates

Quoted from www.githubstatus.com

14:12 UTC
Investigating
We are investigating reports of impacted performance for some GitHub services.
14:15 UTC
Investigating
We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.
14:33 UTC
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.
14:55 UTC
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.
15:15 UTC
Investigating
We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.
15:24 UTC
Investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
15:26 UTC
Monitoring
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
15:28 UTC
Resolved
On October 28, 2026, between 13:52 and 15:24 UTC, Copilot users saw errors when using several GPT-family models and the MAI Code 1.1 Flash model. Affected experiences included Copilot Chat in IDEs and on GitHub.com, the Copilot CLI, Copilot Code Review, the Copilot Coding Agent, Code Scanning Autofix, and Code Quality. About 9.73% of requests to the affected models failed, with a peak of about 36.97% at the start of the incident.<br /><br />The errors happened because a credential that we use to authenticate with an upstream model provider became invalid. We mitigated the incident by replacing the credential and redeploying the service. We are strengthening how we manage credentials for upstream providers to prevent this type of failure, returning retryable errors when an upstream provider rejects a request, and improving our monitoring so that we detect and mitigate this type of problem faster in the future.

Other GitHub Copilot incidents

Nov 3

31 minIncident with API, Git, and Copilot requests Details

Nov 2

38 minElevated errors on GPT-5.4 Nano Details

Oct 23

42 minGrok 4.6 and Grok 4.7 Service Issues Details

All GitHub Copilot incidents

Other agents

Know the moment it's back.

Coral shows it in your Mac's notch, and tells you which agent needs you. Free.

Get Coral for Mac

GitHub's updates

14:12 UTC

Investigating

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

14:15 UTC

Investigating

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

14:33 UTC

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.

14:55 UTC

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.

15:15 UTC

Investigating

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

15:24 UTC

Investigating

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

15:26 UTC

Monitoring

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

15:28 UTC

Resolved

On October 28, 2026, between 13:52 and 15:24 UTC, Copilot users saw errors when using several GPT-family models and the MAI Code 1.1 Flash model. Affected experiences included Copilot Chat in IDEs and on GitHub.com, the Copilot CLI, Copilot Code Review, the Copilot Coding Agent, Code Scanning Autofix, and Code Quality. About 9.73% of requests to the affected models failed, with a peak of about 36.97% at the start of the incident.<br /><br />The errors happened because a credential that we use to authenticate with an upstream model provider became invalid. We mitigated the incident by replacing the credential and redeploying the service. We are strengthening how we manage credentials for upstream providers to prevent this type of failure, returning retryable errors when an upstream provider rejects a request, and improving our monitoring so that we detect and mitigate this type of problem faster in the future.