GitHub Outage History

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.

GitHub Actions experienced degraded performance, with some workflows not running as expected. The issue affected the Actions component and disrupted CI/CD automation for about 1 hour and 15 minutes. The outage began at Jan 9, 2025 7:16 AM UTC and was resolved by Jan 9, 2025 8:31 AM UTC. The provider issued 2 status updates during the incident, including an initial investigation and later confirmation that Actions had returned to normal.

GitHub experienced an outage beginning at 1:41 AM UTC that affected Webhooks and caused degraded performance across several GitHub services. Affected components included Webhooks, Pages, Pull Requests, Git Operations, Codespaces, Copilot, API Requests, Issues, and Actions. Users reported sign-in errors, 500 server responses, and issues creating or updating pull requests and codespaces.

The incident prompted a series of updates from GitHub detailing ongoing investigation and recovery. The provider issued 7 status updates during the event. The outage began at 1:41 AM UTC and was resolved by 2:31 AM UTC, lasting about 50 minutes. Recovery progressed with Copilot and other components returning to normal across the timeline, and all listed services were back online by the final update.

GitHub experienced degraded performance across Actions, with Issues and Webhooks also showing degradation. Users saw slower automated workflows, delays in issue activity, and laggy webhook events. The incident began around Jan 7, 2025 2:49 PM UTC and persisted for approximately 1 hour and 52 minutes, until Jan 7, 2025 4:41 PM UTC. The impact covered three components: Actions, Issues, and Webhooks. The provider issued four official updates between Jan 7, 2025 2:51 PM UTC and Jan 7, 2025 4:41 PM UTC explaining ongoing investigations and progress, with all components restored by the end.