GitHub Outage History

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.

GitHub experienced a brief degradation affecting the Pull Requests component, causing limited performance for related workflows. The incident began at Apr 7, 2025 2:26 AM UTC and was resolved by Apr 7, 2025 2:31 AM UTC, lasting about 5 minutes. The GitHub Status page noted that Pull Requests was experiencing degraded performance and that teams were actively investigating, with two official updates issued during the incident. The impact was localized to Pull Requests, with other GitHub services remaining available.

GitHub Codespaces entered a scheduled maintenance window from Apr 2, 2025 5:01 PM UTC to Apr 3, 2025 5:01 PM UTC. During this period, Codespaces was listed as under maintenance, which may have caused intermittent access or degraded performance for users attempting to use Codespaces. A small number of user reports were logged during the window from multiple regions, including Chennai, India and Taldykorgan, Kazakhstan, indicating activity around this service during the maintenance. The maintenance duration was 24 hours.

GitHub reported degraded performance in the Pull Requests component due to a disruption with PR Ref Updates. The incident began at 11:56 PM UTC and was resolved by 1:41 AM UTC, lasting about 1 hour and 45 minutes. Users relying on PR references and related workflows may have experienced slower updates or delays during this period. The issue was limited to the Pull Requests area and did not indicate a broader service outage.

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.