Skip to main content

GitHub Copilot · 75d ago

Latency issues across a number of services

Resolved

Yes — GitHub Copilot had a problem on July 23, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident. <br /><br />The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered. <br /><br />To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot.”

See GitHub Copilot's live status →

Timeline

Started: 7/23/2026, 7:53:59 AM

Last update: 7/27/2026, 9:51:04 PM

Resolved: 7/23/2026, 9:39:19 AM

Affected: 4230lsnqdsld, kr09ddfgbfsf, hhtssxt0f5v2, br0l2tvcx85d

GitHub Copilot's official report →

Updates

  • resolved

    On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident. <br /><br />The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered. <br /><br />To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot.

    7/23/2026, 9:39:19 AM

  • monitoring

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

    7/23/2026, 9:39:11 AM

  • investigating

    Webhooks is operating normally.

    7/23/2026, 9:35:17 AM

  • investigating

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

    7/23/2026, 9:27:35 AM

  • investigating

    We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

    7/23/2026, 9:22:21 AM

  • investigating

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

    7/23/2026, 9:19:49 AM

  • investigating

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

    7/23/2026, 9:18:37 AM

  • investigating

    We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

    7/23/2026, 8:34:23 AM

  • investigating

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

    7/23/2026, 8:25:16 AM

  • investigating

    We are investigating reports of degraded availability for Actions, Issues and Webhooks

    7/23/2026, 7:53:59 AM

More GitHub Copilot incidents

Is GitHub Copilot down right now?All outage history →

Is GitHub Copilot down? GitHub Copilot is up now — Jul 23, 2026 outage | AI Status