GitHub incident

Disruption with some GitHub services

Minor Resolved View vendor source →

GitHub experienced a minor incident on September 15, 2026 affecting Copilot AI Model Providers, lasting 1h 30m. The incident has been resolved; the full update timeline is below.

Started
Sep 15, 2026, 09:47 AM UTC
Resolved
Sep 15, 2026, 11:17 AM UTC
Duration
1h 30m
Detected by Pingoru
Sep 15, 2026, 09:47 AM UTC

Affected components

Copilot AI Model Providers

Update timeline

  1. investigating Sep 15, 2026, 09:47 AM UTC

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

  2. monitoring Sep 15, 2026, 09:48 AM UTC

    We are investigating degraded availability for Claude Fable 5.1, affecting some Copilot products and integrated development environments. The issue is caused by a problem with our upstream model provider. Customers can use another model or select Auto while we investigate.

  3. investigating Sep 15, 2026, 10:20 AM UTC

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

  4. investigating Sep 15, 2026, 10:32 AM UTC

    We continue to investigate intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customers can use another model or select Auto while we monitor the situation.

  5. investigating Sep 15, 2026, 11:09 AM UTC

    We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers can select another model or Auto in the meantime.

  6. investigating Sep 15, 2026, 11:17 AM UTC

    The issues with our upstream model provider have been resolved, and Claude Fable 5.1 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

  7. resolved Sep 15, 2026, 11:17 AM UTC

    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.