GitHub Outage History

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.

GitHub Pages and GitHub Actions experienced degraded performance, impacting builds and published pages. Users may have encountered slower deployments and delays in page publishing during the incident. The issue affected two components: Pages and Actions.

The GitHub Codespaces service experienced degraded performance beginning at 3:04 PM UTC, with users reporting slower environments and intermittent issues for Codespaces. The disruption persisted for about 2 hours and 52 minutes, until 5:56 PM UTC.

GitHub experienced a brief degradation in the Git Operations component when unauthenticated LFS requests for public repositories started returning 401 errors. Users may have encountered authentication-related failures during LFS operations. The incident began around 5:45 PM UTC as user reports appeared, progressed to a degraded state at 6:06 PM UTC, and was resolved by 6:31 PM UTC when status returned to normal. The GitHub status page issued 2 updates during the event, noting the degraded performance and ongoing investigation.

GitHub Actions experienced a brief degradation affecting automated workflows. The GitHub Status page flagged an incident with Actions and described investigations beginning around 1:23 PM UTC. The Actions component moved to degraded at 1:26 PM UTC and the service was restored by 2:06 PM UTC, for a total duration of about 43 minutes. The incident included two official status updates detailing the investigation and resolution.