GitHub Outage History

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.

An incident began on 7:06 PM UTC with GitHub Actions reporting degraded performance that escalated to a full outage for hosted runners by 7:46 PM UTC. The disruption blocked many CI/CD workflows as jobs queued or failed. Over the next hours, additional GitHub components were impacted: Codespaces showed degraded performance starting at 8:21 PM UTC, and Copilot and Pages also experienced issues as the incident progressed. User reports from around the world described stalled builds, waiting runners, and trouble creating or resuming codespaces, indicating broad impact.

GitHub's status page documented ongoing investigations and multiple updates through the incident, with teams describing degraded services and progress toward mitigation. Recovery began around 12:56 AM UTC as Actions and Codespaces returned to normal operation; Pages and Copilot issues were also resolved in subsequent updates. The outage lasted approximately 5 hours and 50 minutes, affecting four major GitHub components.

GitHub reported a disruption affecting Git Operations, resulting in degraded performance across a subset of GitHub services. Users may have experienced slower repository interactions during the incident. The issue began at 5:36 PM UTC and was resolved by 5:46 PM UTC.

GitHub experienced a brief degradation in Actions affecting Run Start for workflows. The incident began with an investigation at Jan 28, 2026 3:12 PM UTC and the Actions component was listed as degraded at Jan 28, 2026 3:16 PM UTC. The disruption lasted approximately 44 minutes and was resolved by Jan 28, 2026 3:56 PM UTC.

GitHub communicated the incident via its status page, noting the investigation and subsequent restoration. The service issued two status updates during the event. User reports were limited, and there was no clear regional pattern.

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.

An outage impacted four GitHub components—Pull Requests, API Requests, Issues, and Actions—causing errors and degraded performance for users trying to create or review pull requests, manage issues, or call API endpoints. The disruption began at Jan 15, 2026 5:01 PM UTC and lasted until Jan 15, 2026 6:56 PM UTC. StatusGator detected the issue at Jan 15, 2026 4:52 PM UTC, about 9 minutes before GitHub's first acknowledgment at Jan 15, 2026 5:01 PM UTC. The GitHub Status Page issued 7 updates during the incident, noting degradation across API Requests, Issues, Pull Requests, and Actions, with recovery announced progressively until all components returned to normal by Jan 15, 2026 6:56 PM UTC. User reports indicated broad, global impact, consistent with a widespread incident.