GitHub Outage History

During a scheduled maintenance window that began at 4:30 PM UTC, GitHub started with Codespaces listed under maintenance. By 3:20 PM UTC, users reported degraded performance across Git Operations and related workflows, including Pull Requests and Actions. The incident affected four core components: Git Operations, Pull Requests, Actions, and Codespaces. Status updates described ongoing investigations and gradual recovery, and all services were reported back to normal by May 8, 2025 4:31 PM UTC. The incident persisted for roughly 24 hours from the start of maintenance to full restoration, with user reports submitted from multiple locations.

Impact and recovery: Developers could experience slower commits, intermittent pull requests, and delayed or failing Actions workflows, as well as limited access to Codespaces during the window. GitHub issued five official updates during the incident to communicate progress, with Git Operations and Codespaces restored first, followed by Pull Requests and Actions. The overall service was restored by the end of the day on May 8, 2025.

GitHub experienced a brief outage affecting the Issues component, with attachments failing to upload. The incident began at May 1, 2025 10:32 PM UTC and was resolved by May 1, 2025 11:16 PM UTC, lasting about 44 minutes. GitHub issued two status updates during the incident: the first noted an investigation into attachment upload failures on Issues, and the second confirmed that the issue was resolved and service restored. The impact was limited to the attachment upload feature within GitHub Issues, with other GitHub services remaining operational.

An issue affecting GitHub.com Pull Requests caused delays and failures in updating PR tracking refs due to processing delays. The incident began at Apr 30, 2025 8:56 PM UTC and lasted about 10 minutes, with PR refs not updating as expected.

GitHub experienced elevated latency across Git Operations, API Requests, and Issues, causing timeouts and slow responses when loading Pull Requests. Some users also reported Codespaces pages stalling. The outage affected four components in total (Git Operations, API Requests, Issues, and Pull Requests), resulting in a degraded user experience for developers. The outage began on Apr 28, 2025 8:06 AM UTC and was resolved by Apr 28, 2025 11:11 AM UTC, lasting about 3 hours and 5 minutes. During the incident, GitHub posted three status updates detailing the Issues API latency and related components, and confirming when services were returning to normal.

GitHub experienced a brief degraded performance affecting API Requests, Issues, and Pages, with Codespaces and Actions also listed as affected. The incident began at 7:21 AM UTC when the status page indicated a degraded state and user reports described slower API responses and delays in issue creation and page loads. The impact appeared global, affecting multiple GitHub services for a portion of users.

GitHub issued three official updates during the incident as investigation continued. The issue was resolved by 7:46 AM UTC, with all components returning to normal. The outage lasted about 25 minutes. The affected components included API Requests, Issues, Pages, Codespaces, and Actions.

GitHub Codespaces underwent a scheduled maintenance window from Apr 21, 2025 4:31 PM UTC to Apr 22, 2025 4:31 PM UTC. During this period, the Codespaces component was listed as under maintenance, which could have resulted in limited access or degraded performance for users attempting to work in Codespaces. GitHub's Status page noted the maintenance in progress and posted updates as the work continued, with two official status updates during the incident. A small amount of user feedback during the window indicated some connectivity issues, including observations from Delhi, India.

GitHub Pull Requests experienced degraded performance beginning around 3:22 PM UTC, with users reporting slow loading and intermittent failures when creating, reviewing, or merging pull requests. The incident was shown on GitHub Status as an ongoing investigation for the Pull Requests component starting at 3:22 PM UTC.

Two status updates were issued during the incident. The Pull Requests component moved from up to degraded at 3:26 PM UTC and then returned to up at 5:31 PM UTC. The outage lasted roughly 2 hours and 9 minutes. A user in the United Kingdom reported site issues during the early phase around 3:27 PM UTC.

GitHub Codespaces experienced a brief outage, interrupting access to development environments. The disruption began at Apr 11, 2025 12:31 AM UTC when GitHub listed degraded availability for Codespaces and started investigating; Codespaces was restored at Apr 11, 2025 12:56 AM UTC. The incident prompted two official status updates, and the impact appears limited to the Codespaces component with no reported issues across other GitHub services. Users likely experienced temporary interruptions while using Codespaces during the 25-minute window.

GitHub experienced a partial outage in the Pull Requests component, causing delays in PR updates. After pushing new commits, some pull requests showed a 'Processing updates' state, and new commits did not appear in the PR view for affected users.

The outage began on Apr 9, 2025 11:41 PM UTC and lasted about 1 hour, with the issue resolved by Apr 10, 2025 12:41 AM UTC. The GitHub status page issued 2 updates during the incident, describing the disruption and the resolution. The problem was isolated to Pull Requests and did not reflect broader problems across GitHub services.

GitHub reported a brief degradation in Pull Requests, impacting creation and review workflows for about 36 minutes from Apr 9, 2025 9:01 AM UTC to Apr 9, 2025 9:36 AM UTC. Early user reports started around 8:00 AM UTC and continued through 8:30 AM UTC, indicating developer-facing disruption before official acknowledgment. GitHub posted two status updates: first noting an investigation into degraded Pull Requests, and later restoring normal operation at Apr 9, 2025 9:36 AM UTC. The issue affected the Pull Requests component and did not appear to impact other GitHub services.