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

ResolvedResolved1 version

Facts

Source
GitHub Status · original
Started
(4 days ago)
Ended
· lasted 49 min
How it ended
Microsoft marked it resolved.
First captured by us
Last changed
(43 min ago)
Affected services
GitHub Copilot, GitHub Copilot AI model providers

Last text from Microsoft

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.

Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.

Official updates

Posted by GitHub Status, newest first.

  1. 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.

  2. Monitoring

    The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability.

  3. Monitoring

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

  4. Investigating

    Copilot is operating normally.

  5. Investigating

    Copilot AI Model Providers is experiencing degraded availability. We are continuing to investigate.

  6. Investigating

    We are experiencing degraded availability for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. We recommend choosing another model or selecting Auto to continue using Copilot until the issue is resolved.

  7. Investigating

    We are investigating reports of degraded availability for Copilot

What Microsoft changed

Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.

  1. First version we captured

    Captured · Microsoft's own timestamp · revision sd07blrk
    Original text as we first saw it

    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.