GitHub Outage History

GitHub reported a degradation in the GitHub Actions cache service that affected workflows relying on cached artifacts. Users may have experienced slower cache access or misses during the incident. The issue began at 12:31 PM UTC and was resolved by 1:36 PM UTC, lasting about 1 hour and 5 minutes. GitHub issued two status updates during the incident and applied mitigations, with the Actions component returning to normal after the outage.

GitHub experienced a period of degraded performance beginning at 7:21 AM UTC with investigations into API Requests and Git Operations. Over the next several hours, additional components were affected, including Issues, Actions, Packages, and Copilot. Users worldwide reported slow responses and difficulties accessing features such as repositories, issue tracking, and code collaboration. The outage lasted about 2 hours and 30 minutes before components began recovering.

GitHub's status page issued six official updates during the incident, with updates at 7:26 AM UTC, 7:36 AM UTC, 8:26 AM UTC, 8:41 AM UTC, 9:46 AM UTC, and 9:51 AM UTC. By 9:51 AM UTC, services across API Requests, Git Operations, Issues, Actions, Packages, and Copilot had returned to normal. The incident appeared globally, with user reports from Europe, North America, and Asia-Pacific indicating widespread impact.

GitHub API Requests experienced a brief degradation impacting API call latency for a short period. The issue began at 6:31 PM UTC and was resolved by 6:36 PM UTC, lasting about 5 minutes. User reports started arriving around 6:15 PM UTC with 2 observations. GitHub issued 2 status updates during the incident, noting degraded API performance and later confirming restoration. The impact appeared limited to the API Requests component, with no widespread service disruption reported.

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.