GitHub Outage History

The GitHub service experienced a brief outage that prevented users from downloading repository archives containing Git LFS objects. The disruption began at Feb 12, 2026 10:42 AM UTC and was resolved by Feb 12, 2026 11:16 AM UTC, lasting about 34 minutes. User reports were present around 9:30 AM UTC prior to the incident, indicating some early visibility from the community. The impact appeared limited to archival downloads rather than a full platform outage.

GitHub’s status page published two official updates during the incident, acknowledging the disruption and that engineers were investigating, followed by confirmation of restoration. The outage primarily affected attempts to download archives with Git LFS objects rather than indicating a broader service failure.

The GitHub Codespaces outage began at Feb 12, 2026 7:56 AM UTC with degraded availability across the Codespaces environment. The issue escalated to degraded performance, and by Feb 12, 2026 9:46 AM UTC the status page listed Codespaces as degraded while teams continued to investigate. The outage lasted about 2 hours, ending with a recovery around Feb 12, 2026 9:56 AM UTC.

GitHub issued three status updates during the incident to communicate the progression: the initial notification of investigation, a follow-up noting degraded performance, and the final recovery confirmation. The disruption affected the Codespaces component and impacted users worldwide, with reported access and usage issues across multiple regions.

The GitHub status page reported a disruption affecting some services starting Feb 11, 2026 7:01 PM UTC, leading to degraded performance and intermittent access for a subset of GitHub features. Users in Ottawa and Kowloon reported slower responses and occasional access issues, indicating a broad yet partial impact. The incident persisted for about 6 hours and was resolved by Feb 12, 2026 1:01 AM UTC.

During the incident, the GitHub Status page issued two updates describing the disruption and its resolution. The event drew limited user feedback, reflecting a small but noticeable impact on a portion of users.

GitHub experienced increased latency in GraphQL traffic, degrading API Requests and Copilot for some users. The incident began at Feb 11, 2026 3:31 PM UTC and prompted status changes on the affected components. User reports started around 3:00 PM UTC, describing slower GraphQL responses and Copilot-related messages.

Copilot recovered by 3:51 PM UTC, while API Requests returned to normal later at 5:16 PM UTC. The GitHub status page issued 3 updates during the incident, documenting ongoing investigation and eventual restoration. The outage lasted about 1 hour and 45 minutes and affected GraphQL-dependent workflows during the window.

The GitHub Copilot feature experienced failures as requests could not be processed due to an unsupported API version. The issue began at 1:54 AM UTC and affected Copilot usage globally, with error messages indicating the API version is no longer supported. Users reported Copilot errors and related failures across multiple regions, reflecting a broad impact on how Copilot interacted with GitHub services. The incident was observed through user reports rather than official status updates.

GitHub's Pull Requests component experienced degraded performance from Feb 10, 2026 3:11 PM UTC to Feb 10, 2026 4:01 PM UTC, impacting PR creation, reviews, and related checks for about 50 minutes. Users across multiple regions reported issues with PR workflows and CI steps during the incident, including sporadic failures in some actions steps and unusual page behavior.

GitHub communicated via two status updates: the first at Feb 10, 2026 3:11 PM UTC noting Disruption with some GitHub services and that Pull Requests was experiencing degraded performance while investigations continued, and the second at Feb 10, 2026 4:01 PM UTC indicating the Pull Requests component had returned to normal. The incident affected 1 component and included 2 status updates.

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.