Outage recap · GitHub

GitHub Copilot outage — November 4, 2026

On November 4, 2026, GitHub Copilot had 4 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.

Increased task-related errors for Copilot Mission Control

minor
Started
Nov 4, 3:45 AM EST
Resolved
Nov 4, 5:01 AM EST
Duration
1h 17m

GitHub's updates (6)

  1. investigating · Nov 4, 3:45 AM EST

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

  2. investigating · Nov 4, 3:47 AM EST

    Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations.

  3. investigating · Nov 4, 4:11 AM EST

    We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.

  4. investigating · Nov 4, 4:50 AM EST

    We're continuing to see recovery as rollout continues

  5. monitoring · Nov 4, 5:01 AM EST

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

  6. resolved · Nov 4, 5:01 AM 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 16 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 453 ms, against 450 ms over the 24 hours before. GitHub posted the incident at Nov 4, 3:45 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 ↗

Incident with Pull Requests, Git Operations and Issues

major
Started
Nov 4, 4:49 AM EST
Resolved
Nov 4, 6:50 AM EST
Duration
2h

GitHub's updates (9)

  1. investigating · Nov 4, 4:49 AM EST

    We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests

  2. investigating · Nov 4, 4:50 AM EST

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

  3. investigating · Nov 4, 4:53 AM EST

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

  4. investigating · Nov 4, 5:38 AM EST

    We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.

  5. investigating · Nov 4, 6:11 AM EST

    API Requests is experiencing degraded performance. We are continuing to investigate.

  6. investigating · Nov 4, 6:17 AM EST

    We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.

  7. investigating · Nov 4, 6:30 AM EST

    The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

  8. monitoring · Nov 4, 6:43 AM EST

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

  9. resolved · Nov 4, 6:50 AM 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 24 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 581 ms, against 450 ms over the 24 hours before. GitHub posted the incident at Nov 4, 4:49 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 ↗

Incident with Actions and Pages

major
Started
Nov 4, 11:05 AM EST
Resolved
Nov 4, 12:01 PM EST
Duration
56 min

GitHub's updates (9)

  1. investigating · Nov 4, 11:05 AM EST

    We are investigating reports of degraded performance for Actions and Pages

  2. investigating · Nov 4, 11:11 AM EST

    We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.

  3. investigating · Nov 4, 11:12 AM EST

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

  4. investigating · Nov 4, 11:17 AM EST

    Actions is experiencing degraded availability. We are continuing to investigate.

  5. investigating · Nov 4, 11:34 AM EST

    We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.

  6. investigating · Nov 4, 11:45 AM EST

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

  7. monitoring · Nov 4, 11:48 AM EST

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

  8. monitoring · Nov 4, 11:49 AM EST

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

  9. resolved · Nov 4, 12:01 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 430 ms, against 452 ms over the 24 hours before. GitHub posted the incident at Nov 4, 11:05 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 ↗

Incident with Actions

major
Started
Nov 4, 12:40 PM EST
Resolved
Nov 4, 1:16 PM EST
Duration
36 min

GitHub's updates (4)

  1. investigating · Nov 4, 12:40 PM EST

    We are investigating reports of degraded availability for Actions

  2. investigating · Nov 4, 12:53 PM EST

    We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.

  3. monitoring · Nov 4, 1:07 PM EST

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

  4. resolved · Nov 4, 1:16 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 7 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 444 ms, against 452 ms over the 24 hours before. GitHub posted the incident at Nov 4, 12:40 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.