Outage recap · GitHub

GitHub Copilot outage — November 5, 2026

On November 5, 2026, GitHub Copilot had 2 reported incidents on GitHub's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Incident with Actions

minor
Started
Nov 5, 11:50 AM EST
Resolved
Nov 5, 12:42 PM EST
Duration
52 min

GitHub's updates (4)

  1. investigating · Nov 5, 11:50 AM EST

    We are investigating reports of degraded performance for Actions

  2. investigating · Nov 5, 11:52 AM EST

    Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.

  3. monitoring · Nov 5, 12:04 PM EST

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

  4. resolved · Nov 5, 12:42 PM EST

    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.

What our checks recorded

We checked GitHub Copilot 11 times from GitHub's start time to its resolution, once every five minutes. Every one of them reached GitHub Copilot's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 469 ms, against 439 ms over the 24 hours before. GitHub posted the incident at Nov 5, 11:50 AM EST.

Updates are GitHub's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Degraded performance for multiple GitHub services

minor
Started
Nov 5, 6:36 PM EST
Resolved
Nov 5, 7:20 PM EST
Duration
45 min

GitHub's updates (8)

  1. investigating · Nov 5, 6:36 PM EST

    We are investigating reports of degraded performance for Actions and Pages

  2. investigating · Nov 5, 6:36 PM EST

    We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC.

  3. investigating · Nov 5, 6:58 PM EST

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

  4. monitoring · Nov 5, 7:06 PM EST

    The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability.

  5. monitoring · Nov 5, 7:06 PM EST

    We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC.

  6. investigating · Nov 5, 7:19 PM EST

    Git Operations is operating normally.

  7. monitoring · Nov 5, 7:19 PM EST

    This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report.

  8. resolved · Nov 5, 7:20 PM EST

    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.

What our checks recorded

We checked GitHub Copilot 9 times from GitHub's start time to its resolution, once every five minutes. Every one of them reached GitHub Copilot's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 491 ms, against 447 ms over the 24 hours before. GitHub posted the incident at Nov 5, 6:36 PM EST.

Updates are GitHub's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Is GitHub Copilot down right now? →GitHub Copilot status history →

AIDownCheck is not affiliated with GitHub. This recap summarizes incidents published on GitHub's official status page.