GitHub Outage History

GitHub experienced a brief partial outage affecting file uploads across some services. User reports began around 10:00 PM UTC, suggesting upload issues before official acknowledgement. The GitHub Status page listed a degraded state at Feb 13, 2026 10:36 PM UTC and noted that investigators were looking into disrupted performance for some GitHub services. The outage lasted approximately 25 minutes and was resolved by Feb 13, 2026 11:01 PM UTC. The provider issued two status updates during the incident to communicate investigation and restoration progress.

The outage began at Feb 12, 2026 6:36 PM UTC when GitHub flagged a disruption affecting some services and said it was investigating impaired performance. The issue persisted for roughly two hours and was resolved by Feb 12, 2026 8:36 PM UTC, after which the status returned to up. Users began reporting issues around 7:00 PM UTC UTC, with observations from locations including the United States and France. GitHub issued two status updates during the incident describing the investigation and restoration of services.

The GitHub status page reported an intermittent disruption affecting Copilot completions and inline suggestions, with degraded availability in some regions. Users may have experienced slower or incomplete Copilot responses during the incident. The outage began at Feb 12, 2026 2:11 PM UTC and was resolved by Feb 12, 2026 4:51 PM UTC, lasting roughly 2 hours and 40 minutes.

The status page issued two updates during the incident, noting the degraded availability and that engineers were actively working to resolve the problem. By Feb 12, 2026 4:51 PM UTC, the service had returned to normal. Impact was centered on Copilot features in affected regions, with no broader GitHub services reported as affected.

GitHub experienced a brief outage that prevented downloading repository archives containing Git LFS objects. The disruption began at 10:42 AM UTC and was resolved by 11:16 AM UTC, lasting approximately 34 minutes. A small volume of user reports appeared around the start of the incident, indicating limited issues from end users.

GitHub's status page described the event as a disruption affecting some services and noted an ongoing investigation into downloads of archives that include Git LFS objects. The service issued two official updates during the incident, and the affected functionality returned to normal after the second update.

The GitHub Codespaces outage began at 7:56 AM UTC with degraded availability for Codespaces. Users reported not being able to open Codespaces or experiencing slow performance, disrupting development workflows for developers relying on Codespaces. The incident affected the Codespaces component and persisted for roughly 2 hours until restoration.

GitHub posted three status updates during the incident at Feb 12, 2026 7:56 AM UTC, Feb 12, 2026 9:46 AM UTC, and Feb 12, 2026 9:56 AM UTC as it investigated and worked toward restoration. The issue appeared global with reports from multiple regions indicating broad impact.

GitHub began experiencing degraded performance across a subset of services beginning at Feb 11, 2026 7:01 PM UTC. Users reported slower response times and intermittent errors when accessing various GitHub features, with the impact lasting for about 6 hours before services returned to normal at Feb 12, 2026 1:01 AM UTC. The incident affected users across different regions, with reports indicating issues in multiple locations.

GitHub reported an incident where GraphQL traffic experienced increased latency, affecting API requests and Copilot features. This led to slower responses for GraphQL calls and intermittent Copilot behavior during the window. The incident began at Feb 11, 2026 3:31 PM UTC and involved the Copilot and API Requests components. Copilot degraded early and recovered by 3:51 PM UTC, while API Requests remained degraded until Feb 11, 2026 5:16 PM UTC.

Over the course of the incident, GitHub issued three official status updates reflecting the progression from degraded performance to restoration for the affected components. The outage lasted roughly 1 hour and 45 minutes, with user experiences indicating slower GraphQL operations and sporadic Copilot prompts during the incident period.

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.

The GitHub Pull Requests service experienced degraded performance lasting about 50 minutes, affecting PR-related actions such as creation, review, and CI checks. The incident began on 3:11 PM UTC when GitHub listed the Pull Requests component as degraded and was resolved by 4:01 PM UTC. User reports started around 2:30 PM UTC and continued through the incident, including issues like 403 errors in GitHub Actions and odd page displays.

GitHub posted two status updates during the incident, noting ongoing investigation and eventual restoration of normal service. The reports came from users across multiple regions, indicating a broad impact on PR workflows before full recovery by 4:01 PM UTC.

GitHub experienced a significant outage starting at Feb 9, 2026 4:21 PM UTC, affecting core collaboration and automation features. Users faced delayed notifications and widespread degradation across Pull Requests, Issues, Actions, Webhooks, Pages, Git Operations, Packages, Codespaces, and Copilot policy propagation delays. The incident disrupted repository work and CI workflows, with reports of failed merges, slow pages, and delayed or missing policy updates for newly enabled models across multiple regions worldwide. The outage persisted for many hours, with impact visible across regions as the situation evolved.

Status updates on GitHub's status page described ongoing investigations and phased recoveries. The company published multiple updates detailing degradation and staged restoration across the affected components. Recovery progressed in waves, bringing Pull Requests, Issues, Actions, Webhooks, Pages, Git Operations, Packages, Codespaces, and Copilot back toward normal operation. By Feb 10, 2026 10:01 AM UTC, most services had recovered and the incident was substantially resolved, though some backlogs briefly fluctuated as systems stabilized.