GitHub Outage History

GitHub's API Requests component experienced degraded performance, impacting users making API calls. Developers reported slower responses and occasional failures across regions. The outage began at 2:29 PM UTC and was first acknowledged at 2:31 PM UTC; the service remained degraded until 3:56 PM UTC when it returned to normal, for a duration of about 1 hour and 27 minutes.

GitHub's status page documented the investigation and subsequent recovery. The API Requests component moved from up to warn and back to up across two official updates during the incident. User reports indicated global distribution, with activity from multiple regions reporting API errors and slow responses.

GitHub Actions experienced degraded performance, impacting workflows that rely on Actions. Users reported very slow builds and delays in job execution across multiple regions. The issue was isolated to the Actions component. The outage began on 9:12 AM UTC and was resolved by 12:31 PM UTC, lasting about 3 hours and 19 minutes. The provider published 2 status updates during the incident.

GitHub's status page initially indicated an investigation into degraded performance for Actions and later confirmed recovery. Reports from users in various locations corroborate the degraded performance, indicating the impact was observed broadly rather than localized. The Actions component was the affected element throughout the incident.

GitHub Copilot experienced degraded performance for its coding assistance features beginning at 2:46 PM UTC. GitHub reported an investigation into degraded performance affecting the Copilot component, with users potentially noticing slower or less reliable Copilot suggestions during the event. The issue appeared isolated to Copilot and did not list other GitHub services as impacted. The incident lasted about 1 hour 55 minutes, resolving when Copilot returned to normal at 4:41 PM UTC. The GitHub Status page issued two updates during the incident.

The GitHub Codespaces creation service experienced an outage beginning at 8:57 AM UTC with GitHub noting investigations into degraded availability for Codespaces. Users attempting to create Codespaces encountered failures, impacting the Codespaces component and their workflows. The incident prompted GitHub to issue updates describing the degraded availability and ongoing investigation. The outage lasted roughly 2 hours and 4 minutes, resolving by 11:01 AM UTC. A small number of user reports were observed, including a report at 10:30 AM UTC and a sample comment from Madrid at 10:42 AM UTC.

GitHub Copilot experienced degraded performance beginning at 2:06 PM UTC, with reports of errors and slower response times affecting Copilot features. The issue prompted an investigation by GitHub, and the disruption lasted about 1 hour and 55 minutes. Copilot returned to normal by 4:01 PM UTC. The incident appeared isolated to Copilot and did not involve other GitHub services. The provider issued 2 official status updates during the incident.

An outage affected the GitHub Webhooks service and several dependent components, causing delayed webhook deliveries and degraded workflows for developers. Users reported issues with pushes, pull requests, and automated actions across multiple repositories as the Webhooks service and connected components struggled to respond. The outage began at Oct 9, 2025 3:34 PM UTC and was resolved by Oct 9, 2025 4:37 PM UTC, lasting about 1 hour and 3 minutes.

StatusGator detected the issue at Oct 9, 2025 3:34 PM UTC, about 7 minutes before GitHub acknowledged the problem on its status page (first update at Oct 9, 2025 3:41 PM UTC). GitHub issued 7 status updates during the incident, as Webhooks and several related components moved through degraded states before recovery. The outage impacted 6 components: Webhooks, Pull Requests, Issues, Actions, Git Operations, and Pages, with recovery progressing over the course of the incident.

The GitHub Webhooks service experienced an outage starting at Oct 9, 2025 2:46 PM UTC, triggering degraded availability across several core GitHub features. The incident affected 7 components, including Webhooks, Actions, Issues, API Requests, Pages, Pull Requests, and Git Operations, with users reporting failed automation, stalled workflows, and deployment issues across multiple regions worldwide. The disruption highlights how critical automated pipelines and CI/CD tasks are to daily development work.

GitHub Copilot experienced a brief degradation beginning at 2:46 AM UTC when Copilot moved to a degraded state. GitHub noted a degraded experience across Anthropic models and that they were working with partners to restore service. The issue lasted about 1 hour and 5 minutes and was resolved by 3:51 AM UTC as Copilot returned to normal. GitHub issued 2 status updates during the incident.

GitHub Actions on macOS runners began degrading at Oct 1, 2025 8:11 AM UTC, impacting CI workflows that rely on macOS runners. Later that day, Copilot Gemini 2.5 Pro reported degraded performance across Copilot Chat, VS Code, and other Copilot products, with the maximum input length of Gemini 2.5 prompts reduced and long prompts or large context windows potentially erroring due to an upstream model provider issue. Users may have experienced slow interactions or failures when using Copilot features during this period. Over the course of the incident, GitHub issued 4 official status updates. The Actions component recovered by Oct 1, 2025 4:56 PM UTC, while Copilot remained degraded until Oct 2, 2025 10:36 PM UTC when Copilot components were restored. The outage lasted about 1 day, 14 hours, and 25 minutes in total.

GitHub Copilot experienced degraded availability affecting Claude Sonnet 3.7 and Claude Sonnet 4 models across Copilot Chat, VS Code, and other Copilot products. The degradation was due to an upstream model provider issue, with other models remaining available. The incident began on Sep 23, 2025 10:26 PM UTC and lasted about 2 hours before resolution on Sep 24, 2025 12:26 AM UTC.

GitHub's status page noted the upstream provider problem and confirmed that other Copilot models were functioning as expected. Copilot components returned to normal as services recovered.