GitHub Outage History

GitHub Copilot experienced a brief degraded-performance incident lasting about 45 minutes, from Feb 3, 2026 10:16 AM UTC to Feb 3, 2026 11:01 AM UTC. During this window, users likely encountered slower or incomplete Copilot suggestions, while other GitHub services were not affected. GitHub documented the incident with two status updates, including an initial note about an investigation into degraded Copilot performance and a follow-up confirming restoration.

GitHub Copilot users experienced 502 errors when making Copilot requests, disrupting code completion and related features across various IDEs and interfaces. User reports came from around the globe, with activity peaking between 09:45 and 10:00 UTC and subsiding thereafter, indicating a widespread impact across multiple regions.

StatusGator flagged the incident early, with issues detected starting at Feb 3, 2026 9:04 AM UTC based on user reports before any provider updates. The outage lasted about 1 hour and 12 minutes, resolving by Feb 3, 2026 10:16 AM UTC. The event affected users globally rather than being confined to a specific region, underscoring the broad reach of the Copilot service during the incident.

GitHub experienced a multi-service outage beginning at 7:06 PM UTC that degraded GitHub Actions and then cascaded to other services including Pages, Codespaces, and Copilot. Users faced queued Actions jobs, timeouts, and failures when creating or resuming codespaces, with broader performance issues across the platform. The impact was felt by developers across regions as workflows stalled and runtimes struggled.

Over roughly 5 hours and 50 minutes, GitHub issued nine status updates documenting investigation and mitigation steps. By 12:56 AM UTC, Actions and Codespaces had recovered and the affected components returned to normal operation, with Copilot and Pages following suit as updates progressed. The outage thus spanned multiple services and components before a full recovery. The incident appeared global, reflected in widespread user reports from many regions around the world.

The provider’s updates outlined ongoing investigation and remediation efforts, with the timeline showing degradation progressing to a wider impact and then recovery across the major affected components.

GitHub experienced a brief disruption affecting Git Operations, resulting in degraded performance for a short period. The incident began at 5:36 PM UTC and was resolved by 5:46 PM UTC, lasting about 10 minutes. The provider issued 2 status updates during the incident as teams investigated and confirmed restoration. Users may have experienced slower or intermittent Git operations during the outage, with services returning to normal after the final update.

A brief outage affected GitHub Actions when starting runs, causing delays for workflows. The incident began around 3:12 PM UTC with the status page noting an investigation at 3:16 PM UTC and listing the Actions component as degraded. The issue impacted the start of Actions workflows across affected jobs. The provider posted two updates during the incident, and normal service was restored by 3:56 PM UTC, for an outage duration of about 40 minutes. User reports were limited, indicating a relatively small portion of users were affected.

GitHub experienced degraded performance in the Issues feature for a brief period, potentially slowing down creating, viewing, or managing issues for users. The disruption began around 2:23 PM UTC and was resolved by 2:31 PM UTC, lasting roughly 8 minutes. User reports were observed during this window, including some from the Netherlands indicating slower UI responses.

GitHub's status page documented the incident with updates: an initial note at 2:23 PM UTC stating degraded performance and ongoing investigation, and a follow-up at 2:26 PM UTC signaling the issue as a partial outage before returning to normal by 2:31 PM UTC. The incident involved the Issues component and caused a brief, temporary impact before full recovery.

GitHub Copilot Chat experienced a brief degradation that impacted Grok Code Fast 1. The incident began around 11:33 AM UTC, with the status page noting Investigation at 11:36 AM UTC. The Copilot component returned to normal by 12:41 PM UTC, lasting about 1 hour 8 minutes. The GitHub Status page published two updates during the incident, and user reports were limited.

GitHub Actions experienced a brief period of degraded performance affecting run start times. The Actions component moved to a degraded state at around 7:51 PM UTC, after GitHub noted an investigation into reports of degraded performance for Actions at Jan 20, 2026 7:49 PM UTC. The disruption lasted roughly 22 minutes and was resolved by 8:11 PM UTC. A small number of user reports described workflow start delays, and the impact was limited to GitHub Actions.

GitHub's status updates documented the incident. The provider posted two official updates during the event, keeping affected users informed. The outage did not affect GitHub services beyond Actions, and status was restored to normal by the end of the window.

GitHub Actions users relying on actions-runner-controller experienced errors from the auto-scaling APIs, causing a brief disruption for self-hosted runners. The outage lasted about 20 minutes, beginning at 4:06 PM UTC and ending at 4:26 PM UTC. A user reported issues at 3:15 PM UTC ahead of the incident being acknowledged.

GitHub's status page notes the incident started with an update posted at Jan 20, 2026 4:03 PM UTC describing API errors in actions-runner-controller and ongoing mitigation. The issue was resolved by 4:26 PM UTC. The impact appeared concentrated on workflows using the self-hosted runners managed by actions-runner-controller, with users seeing failed auto-scaling operations during the window.

GitHub faced an outage impacting core collaboration features, with Issues and Pull Requests experiencing degraded performance and intermittent errors, and the API endpoints used by automation and integrations showing degraded availability. Users reported difficulties loading issues and PR pages and creating or updating issues or PRs. The incident began at Jan 15, 2026 5:01 PM UTC as API Requests degraded, with GitHub reporting ongoing investigation and mitigation.

Over the course of about 1 hour and 55 minutes, GitHub issued seven status updates outlining the evolving impact across the affected components. API Requests returned to normal by Jan 15, 2026 5:56 PM UTC and Issues and Pull Requests recovered by around Jan 15, 2026 6:56 PM UTC. The disruptions affected 3 components and were observed by users in multiple regions, indicating a broad outage that gradually resolved.