GitHub Outage History

An outage began at 4:21 PM UTC on GitHub, impacting core collaboration and development workflows. Users across the globe experienced degraded performance and outages affecting Pull Requests, Issues, Actions, Webhooks, Pages, Codespaces, Packages, and related services. Notifications were delayed and some operations such as merging PRs or updating issue threads faced disruptions, hindering teamwork.

GitHub's status page issued a sequence of updates throughout the incident as components moved between up, warn, and down states. Recovery progressed gradually, with several services returning to normal at different times. By 5:31 PM UTC many services showed recovery for some components, while others remained degraded for longer. The team continued to investigate and coordinate remediation, with follow-up updates describing backlog processing and continued restoration of features across the platform. The incident persisted across the evening and into the next day, with some services still recovering as late as the following morning, and the status page noting partial resumption until a full recovery was achieved.

GitHub Actions experienced delays starting runs, impacting approximately 4% of users. The incident affected the Actions component and caused workflow start delays. The outage began at Feb 9, 2026 2:21 PM UTC and was resolved by Feb 9, 2026 3:46 PM UTC, lasting about 1 hour and 25 minutes. GitHub issued 2 status updates during the incident while investigating and restoring normal operation. Initial user reports came in around 2:30 PM UTC from Kochi, Kerala, India, indicating impact on workflows for some users.

From Feb 9, 2026 8:16 AM UTC, GitHub reported degraded performance across key workflows, beginning with Pull Requests and Webhooks. Over the next hours, issues expanded to Actions and Git Operations, with intermittent latency and errors across those services. Copilot Coding Agent also experienced degraded availability at one point. The incident affected workflows around PR reviews, automated CI, and webhook-triggered tasks, with reports from multiple regions indicating broad, global impact. The outage lasted about 4 hours and was largely resolved by Feb 9, 2026 12:16 PM UTC. GitHub posted eight status updates during the incident, outlining ongoing investigations, mitigations, and eventual recovery of affected components. User reports came from multiple regions including Germany, Italy, and Pakistan, describing issues like PR reviews being slow or not appearing and Copilot not loading, corroborating the widespread nature of the disruption.

GitHub experienced degraded performance affecting Pull Requests, causing slower PR creation, reviews, and merges. The issue was limited to the Pull Requests component and lasted from 5:51 PM UTC to 6:41 PM UTC (about 50 minutes).

GitHub posted three status updates during the incident: an initial notice at Feb 6, 2026 5:51 PM UTC about degraded performance for Pull Requests; a follow-up at Feb 6, 2026 6:06 PM UTC stating Pull Requests was operating normally; and a final restoration at Feb 6, 2026 6:41 PM UTC confirming the issue was resolved.

GitHub Copilot experienced degraded performance starting at Feb 6, 2026 11:16 AM UTC and was resolved by Feb 6, 2026 12:01 PM UTC, lasting approximately 45 minutes. Users may have encountered slower or less responsive Copilot suggestions during the period. GitHub's status page documented an incident affecting Copilot with an investigation into degraded performance, followed by the Copilot component returning to normal after the incident. The provider issued two status updates during the outage to communicate the investigation and resolution.

GitHub reported degraded performance for GitHub Actions with delays in the user interface for Actions Runs. This affected the visibility and timing of workflow runs, and in some cases prevented runs from starting or completing as expected. Users described issues such as actions not queuing, workflows not triggering, and, in some instances, webhooks not firing, indicating disruption to CI/CD activity.

Timeline and response: The incident began at 4:11 PM UTC when GitHub marked the Actions component as degraded, and was resolved by 7:31 PM UTC when the status returned to normal. The outage lasted about 3 hours and 20 minutes. During the incident, GitHub issued 2 official status updates detailing ongoing investigations and remediation efforts. User reports show a high volume of activity during the peak period, reflecting broad impact on Actions-related workflows.

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.