GitHub outage, 9 November 2026

Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot

Started
Resolved
10 Nov 2026, 00:05 UTC (after 49 min)
Impact
Major
Affected
Copilot, Copilot AI Model Providers

Is this still happening?

No. GitHub marked this incident resolved on 10 Nov 2026, 00:05 UTC, 49 min after it began.

Right now: GitHub reports degraded performance on some systems. (as of 13 Nov, 20:53 UTC) Live GitHub status

At a glance

Our summary from the GitHub incidents we have recorded since 31 Aug 2026 - how we count.

GitHub has said a root cause analysis will follow. We add it to this page when it is posted on the status page.

Last update from GitHub

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.

10 Nov 2026, 00:05 UTC

Read the full incident on the official GitHub status page

Similar GitHub incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , still open

    Copilot experiencing degraded model availability for some GPT models

  2. , resolved after 50 min

    Elevated rate of errors for OpenAI models provided by Copilot

  3. , resolved after 2 h 54 min

    Incident with Grok Copilot AI Model Provider

  4. , resolved after 42 min

    Elevated rate of errors for OpenAI models provided by Copilot

  5. , resolved after 33 min

    Impact across multiple GitHub products including Actions, Pages, and Copilot products.

Other recent GitHub incidents

  1. Incident with Pull Requests

  2. Disruption with Email Delivery

  3. Incident with Webhooks API

  4. Incident with Webhooks

  5. Incident with Git Operations and Pull Requests

  6. Incident with Actions and Checks API

  7. Incident with Webhooks and Actions

  8. Increased timeouts due to surge in anonymous users

All recorded GitHub incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from GitHub's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.