GitHub Outage History

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.

GitHub Actions experienced degraded performance beginning around 10:25 AM UTC, with the Actions component listed as degraded at 10:26 AM UTC as investigators worked to determine the cause. This led to slower workflow runs, longer queue times, and intermittent failures across automation and CI/CD processes for users.

The incident was resolved when the Actions component returned to normal around 5:32 PM UTC. GitHub issued two status updates during the event, and the outage lasted approximately 7 hours and 6 minutes.

GitHub users experienced degraded performance when working with Pull Requests, especially during rebase merge operations. The incident began around Jan 16, 2025 6:22 AM UTC as reports surfaced, and GitHub announced they were investigating the issue. The status was updated to a degraded state for the Pull Requests component at 6:26 AM UTC and the incident was resolved by 9:41 AM UTC, lasting roughly 3 hours and 15 minutes. Two official status updates were issued during the incident, documenting the affected component and the degraded performance.

GitHub Codespaces experienced a brief disruption causing timeouts when creating new Codespaces or connecting to existing sessions. The issue was isolated to the Codespaces component and caused a temporary degradation in access. The disruption began at 8:56 PM UTC and was resolved by 9:21 PM UTC, lasting about 25 minutes.

GitHub posted two status updates during the incident. The first noted disruption and ongoing investigation into timeouts, and the second confirmed Codespaces had returned to normal operation. The impact was confined to Codespaces and resolved within about a half hour.

The GitHub outage began at Jan 13, 2025 11:46 PM UTC and affected the Git Operations component, with Pages and Actions experiencing degraded performance during the incident. This disrupted push operations and CI/workflow executions for a period of about 1 hour and 45 minutes, with user reports coming in from diverse locations worldwide describing errors when pushing code or running workflows. The disturbance impacted three core components in active use by developers.

The GitHub Status page published four updates during the incident, outlining ongoing investigation and degraded status across multiple components. By Jan 14, 2025 12:31 AM UTC, all affected components—Git Operations, Pages, and Actions—had returned to normal operation.