GitHub Outage History

GitHub experienced a brief degradation affecting Actions and Packages. Users running workflows or fetching packages may have encountered slower performance or intermittent failures during the event. The incident began at Feb 26, 2025 3:51 PM UTC and was resolved by Feb 26, 2025 5:21 PM UTC, lasting about 1 hour 30 minutes. The GitHub status page indicated an investigation into degraded performance for Actions and Packages and issued updates as the issue progressed.

The Claude 3.7 Sonnet incident caused Copilot to be partially unavailable with degraded performance. Copilot was listed as degraded from 2:46 PM UTC until 3:46 PM UTC UTC, and GitHub noted that Copilot was experiencing degraded performance while the team investigated.

GitHub Packages experienced degraded performance for a period on Feb 25, 2025 12:17 AM UTC, with the Packages component marked as degraded at Feb 25, 2025 12:22 AM UTC as teams investigated. This impacted workflows relying on GitHub Packages, with users potentially experiencing slower package publishing and downloads.

GitHub Copilot experienced a brief degraded performance when the Claude 3.5 Sonnet model became unavailable, affecting Copilot features. The incident began at 10:06 PM UTC with an official update indicating investigation and was resolved by 10:16 PM UTC, lasting about 10 minutes. The GitHub status page issued 2 updates during the incident, and Copilot returned to normal after the brief disruption.

GitHub reported a partial outage affecting the Issues component starting at Feb 24, 2025 4:08 PM UTC, with degraded performance. By Feb 24, 2025 4:14 PM UTC, Pull Requests also showed degraded performance, impacting two core developer workflows. Users may have experienced slow responses when viewing, creating, or updating issues and pull requests.

GitHub posted three official updates during the incident, describing ongoing investigation and eventual restoration. Services returned to normal by Feb 24, 2025 5:11 PM UTC. The outage lasted roughly 1 hour and 3 minutes.

Starting at Feb 16, 2025 12:11 PM UTC, GitHub reported degraded performance across several core services including API Requests, Issues, Git Operations, Actions, Codespaces, and Webhooks, which could cause slower responses or intermittent failures for users. A follow-up update at Feb 16, 2025 12:24 PM UTC indicated that Pull Requests were also affected. The incident lasted about 35 minutes, with all listed components restored by Feb 16, 2025 12:46 PM UTC. GitHub issued 3 status updates during the incident.

GitHub experienced a partial outage affecting Codespaces, with degraded performance across some GitHub services. A small number of users reported connectivity issues during the event. The disruption began around 8:22 PM UTC and lasted for about 7 hours and 54 minutes.

GitHub Copilot experienced degraded performance as Claude Sonnet became unavailable, impacting Copilot-related coding assistance. The incident began at 9:56 PM UTC and ended by 11:12 PM UTC, for a total duration of about 1 hour and 16 minutes. GitHub issued two status updates during the incident while a small number of user reports indicated partial disruption of Copilot features that rely on Claude Sonnet.

GitHub experienced degraded performance on API Requests starting around Feb 6, 2025 9:42 AM UTC. Users calling GitHub APIs may have seen slower responses or timeouts. The API Requests component was listed as degraded at Feb 6, 2025 9:46 AM UTC as teams began investigating the issue.

The incident prompted two official status updates. The API returned to normal at Feb 6, 2025 11:16 AM UTC, roughly 1 hour and 34 minutes after it began. The outage primarily affected API usage rather than the broader GitHub service, and affected users attempting API access.

The GitHub status page reported an outage affecting Issues and Pull Requests, causing degraded availability and preventing users from loading or interacting with those components. The incident began at 2:31 PM UTC when Issues and Pull Requests moved from up to down, and a surge of user reports around 2:30 PM UTC confirmed the impact. The outage lasted about 1 hour and 10 minutes and was resolved by 3:41 PM UTC, with the affected components returning to an up state.