Skip to main content

GitHub outage on November 13, 2026: Copilot experiencing degraded model availability for some GPT models

GitHub reported an incident affecting GitHub for 1 hour 14 minutes on 13 November 2026, from 20:13 to 21:27 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started
20:13
13 Nov 2026 UTC
Resolved
21:27
13 Nov 2026 UTC
Duration
1h 14m
1 hour 14 minutes
Impact
Minor
as rated by GitHub
Updates
5
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Copilot experiencing degraded model availability for some GPT models

Resolved Minor impact 13 Nov 2026 20:13 UTC View on GitHub's status page
  1. Official
    Investigating

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

  2. Official
    Investigating

    We are experiencing degraded availability for gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra, and gpt-6-luna 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.

  3. Official
    Investigating

    We are in contact with the upstream provider and monitoring as they work towards resolution. For customers who are impacted we recommend choosing another model or selecting ‘Auto’ to continue using Copilot.

  4. Official
    Investigating

    The upstream provider has made mitigations and we are seeing the affected models begin to recover.

  5. Official
    Resolved

    Between 19:05 and 21:27 UTC on November 13, 2026, GitHub Copilot experienced degradation affecting GPT-6.1 Terra, GPT-5.6 Sol, and GPT-6 Luna models. Users encountered elevated error rates when using these models. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.