GitHub Outage History

GitHub experienced degraded performance across API Requests, Issues, and Git Operations, with intermittent timeouts reported by users. Webhooks also showed brief degradation. The incident began at 4:21 AM UTC and was resolved by 5:31 AM UTC, lasting about 1 hour 10 minutes.

Status updates on the GitHub Status page described the sequence: at Mar 3, 2025 4:21 AM UTC investigators were looking into degraded performance across API Requests, Git Operations and Issues. At 4:26 AM UTC Webhooks entered a degraded state. By 5:21 AM UTC Git Operations were reported as operating normally and Webhooks had recovered. By 5:31 AM UTC API Requests and Issues had returned to normal.

GitHub Codespaces underwent a scheduled maintenance window, placing the Codespaces component into maintenance mode and causing temporary disruption to Codespaces access for users. The maintenance window lasted about 9 hours, during which some users may have experienced interruptions in their Codespaces workflows.

Timeline and updates: The maintenance began at 5:00 PM UTC with an official update noting the status change to maintenance at 5:01 PM UTC. Services were fully restored at 2:01 AM UTC. The provider issued 2 official status updates during the incident.

GitHub reported degraded performance for write operations on github.com and api.github.com, affecting Issues and Pull Requests. Users may have experienced slower responses and intermittent delays when creating or updating issues or pull requests. The incident began at Feb 28, 2025 6:31 AM UTC and was resolved by Feb 28, 2025 6:56 AM UTC, lasting about 25 minutes. The GitHub Status page published two updates during the event to communicate the degradation and subsequent recovery, with status changes from up to warn and back to up.

GitHub Actions experienced degraded performance affecting automated workflows and CI tasks. The disruption began at 11:31 AM UTC and was resolved by 12:26 PM UTC, lasting about 55 minutes. The issue affected the Actions component and was described on GitHub's status page as degraded performance with ongoing investigation. GitHub issued 2 status updates during the incident: the initial notice at 11:31 UTC reporting degraded performance and ongoing investigation, and a follow-up at 12:26 UTC confirming resolution and return to normal.

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.