GitHub Outage History

GitHub experienced a brief degradation in GitHub Actions as queued jobs were delayed. The incident affected the Actions component, causing delays in execution of GitHub Actions jobs and impacting workflows relying on automated builds and deployments. The issue began at May 22, 2025 7:46 AM UTC and was resolved by May 22, 2025 9:21 AM UTC, lasting about 1 hour 35 minutes. GitHub published two official updates during the incident describing the delays and restoration of normal service. The issue appeared localized to GitHub Actions and did not indicate broader impacts across other GitHub services.

The GitHub Copilot service experienced a brief degraded performance event. Beginning at May 20, 2025 7:41 PM UTC, the Copilot component was listed as degraded, and users may have noticed slower or less reliable code suggestions during the window. The incident affected only Copilot functionality and did not indicate a broader GitHub service impact.

GitHub documented the investigation on its status page and issued two updates during the incident. The Copilot component returned to normal at May 20, 2025 8:06 PM UTC, with the incident lasting roughly 25 minutes.

GitHub Copilot experienced degraded performance caused by elevated error rates tied to Claude Sonnet 3.7. The impact was limited to Copilot features, with users potentially encountering slower responses or intermittent behavior while using Copilot.

The incident began around 1:10 PM UTC and the Copilot component entered a degraded state. GitHub posted two official status updates during the incident, with the situation returning to normal by 4:12 PM UTC, lasting roughly 3 hours.

GitHub Codespaces underwent scheduled maintenance from May 14, 2025 4:30 PM UTC to May 15, 2025 4:32 PM UTC, during which the Codespaces component was listed as under maintenance. This window caused degraded performance for some users.

User reports described slower performance in some regions, including mentions from India. GitHub posted two status updates—the first indicating maintenance was in progress with updates to come, and a follow-up confirming the maintenance had completed.

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.