GitHub Outage History

GitHub Copilot experienced degraded performance, causing a disruption for Copilot features and affecting a subset of GitHub services. The incident began at 1:01 PM UTC and was resolved by 1:46 PM UTC, lasting roughly 45 minutes. The Copilot component was the primary area affected during this event, as noted in GitHub's status updates.

GitHub issued two status updates during the incident to document the investigation and restoration steps. By 1:46 PM UTC Copilot had returned to normal operation. User reports were limited, with observations from some users.

From Mar 21, 2025 6:21 AM UTC to Mar 21, 2025 9:36 AM UTC, GitHub Actions experienced intermittent failures that disrupted workflow runs for some users. The issue manifested as degraded performance and intermittent errors in Actions, potentially causing builds to fail or be delayed. The impact was focused on the Actions component and did not indicate a broader platform outage. The outage lasted roughly 3 hours and 15 minutes, with limited user reports noting that actions were not working.

The GitHub status page communicated the incident, first noting that investigators were looking into degraded performance for Actions, and later confirming recovery as Actions returned to normal. Two official updates were issued during the event.

GitHub Codespaces experienced degraded performance for about 55 minutes, impacting Codespaces environments with slower startup and reduced responsiveness. Reports began around Mar 21, 2025 2:12 AM UTC and GitHub flagged an investigation at Mar 21, 2025 2:16 AM UTC; the service was restored by Mar 21, 2025 3:11 AM UTC after 2 official status updates. The impact was limited to Codespaces, with no other GitHub services indicated affected.

GitHub Pages experienced degraded performance, affecting page hosting and publishing for some users, while Webhooks delivery also showed degraded performance during the incident. User reports began around 7:45 PM UTC UTC, and GitHub acknowledged the issue around Mar 20, 2025 8:04 PM UTC with Pages degraded. By Mar 20, 2025 8:33 PM UTC Webhooks were also affected as the incident evolved.

The service team provided a couple of official updates during the incident, noting ongoing degradation and continuing investigations. The issues were resolved by Mar 20, 2025 8:56 PM UTC, with Pages and Webhooks returning to normal. The impact was limited to these two components, with a relatively small volume of user reports and no prolonged outage.

GitHub experienced an incident affecting GitHub Actions queue processing during a scheduled migrations maintenance window. Some users reported delays or failures when queuing workflow runs. The degradation began at Mar 18, 2025 11:46 PM UTC and continued until Mar 19, 2025 5:01 AM UTC, lasting about 5 hours and 15 minutes. The maintenance had started earlier at Mar 18, 2025 9:01 PM UTC.

The provider issued four status updates over the course of the incident: at Mar 18, 2025 9:01 PM UTC the page moved from up to maintenance; at Mar 18, 2025 11:46 PM UTC an incident with Actions: Queue Run Failures was reported; at Mar 19, 2025 12:56 AM UTC the status moved to maintenance again; and at Mar 19, 2025 5:01 AM UTC the status returned to up.

GitHub Issues experienced degraded performance, affecting users' ability to load, search, and interact with issues. Users may have seen slower page loads or delays when creating, updating, or commenting on issues. This issue was isolated to the Issues component and did not indicate a wider GitHub outage.

Timeline and response: The outage began at Mar 17, 2025 6:39 PM UTC and was acknowledged shortly after at Mar 17, 2025 6:41 PM UTC as investigators looked into degraded performance for GitHub Issues. The Issues component remained degraded until it was restored by Mar 17, 2025 11:06 PM UTC, lasting about 4 hours and 27 minutes. GitHub issued 2 status updates during the incident to communicate progress.

GitHub reported degraded performance for GitHub Actions after some workflow jobs failed to start. The disruption affected GitHub Actions workflows, causing runs to stall or fail to begin for a period of about 40 minutes. The incident began at 1:31 PM UTC and ended at 2:11 PM UTC, with the Actions component moving from up to warn and back to up as updates were published. Two status updates were issued during the incident, and operation returned to normal after the final update.

GitHub experienced a brief partial outage affecting Actions and Pages. The issue caused start delays for Actions runs (about 40% were not starting within five minutes) and disrupted Pages deployments for GitHub-hosted runners. The incident affected 2 components and lasted about 25 minutes, from Mar 8, 2025 5:51 PM UTC to Mar 8, 2025 6:16 PM UTC.

Status updates indicated progression: by Mar 8, 2025 6:01 PM UTC, Pages was operating normally, and by Mar 8, 2025 6:16 PM UTC the Actions component had returned to normal as well. Over the course of the incident, GitHub issued 3 status updates describing the impact and recovery.

The GitHub incident began at 10:06 AM UTC with Pull Requests experiencing degraded performance. An update at 10:31 AM UTC confirmed that Actions was also degraded, and the update notes referenced Actions being affected around 10:27 AM UTC. Issues similarly reported slower behavior during the event. All affected components—Pull Requests, Actions, and Issues—returned to normal by 11:26 AM UTC, after roughly 1 hour and 20 minutes.

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.