GitHub Outage History

GitHub Copilot experienced degraded performance between Jan 6, 2026 8:56 AM UTC and Jan 6, 2026 10:11 AM UTC. The Copilot component was impacted, causing slower or less reliable code suggestions for users.

The incident lasted about 1 hour and 15 minutes, with GitHub issuing 2 status updates during the event. Copilot was restored to normal performance by the end of the period.

The incident caused a 35-minute outage affecting GitHub's Issues and Pull Requests search indexing, leading to search results being up to three minutes out of date due to elevated processing times in the indexing pipeline. The outage began at 10:01 AM UTC and was resolved by 10:36 AM UTC. Users might have seen stale data when searching for issues or pull requests during the event. GitHub posted updates acknowledging the indexing delays and the plan to restore normal performance, with the affected components returning to normal after the incident.

GitHub experienced degraded performance in the Issues component, with disruptions affecting some GitHub services. The Issues feature entered a degraded state at 10:51 PM UTC and was resolved by 12:21 AM UTC, lasting about 1 hour 30 minutes. Users reported difficulties accessing or updating issues during the incident.

GitHub's status page logged 2 updates during the incident, confirming the degradation and subsequent recovery. The impact was confined to the Issues component, with no broader service-wide outages reported. The initial user activity spiked around the onset and then diminished after the issue was resolved.

The GitHub Copilot service experienced degraded performance for about 25 minutes on Dec 18, 2025 6:46 PM UTC. The incident affected Copilot only, while other GitHub services remained operational. The status page indicated an ongoing investigation as Copilot was degraded, and the issue was resolved by Dec 18, 2025 7:11 PM UTC when Copilot returned to normal. The provider issued 2 status updates during the incident. User reports were minimal, including observations from Paris, indicating limited impact beyond Copilot.

GitHub-hosted Actions runners experienced intermittent networking failures affecting runner setup and workflow execution. Self-hosted runners were not impacted. The incident began around 8:00 AM UTC and the GitHub status page first reported a warning at 4:46 PM UTC, with the issue resolved by 5:46 PM UTC for an approximate duration of 9 hours 46 minutes. The event prompted two official status updates during the period.

The Grok Code Fast 1 model used in GitHub Copilot products experienced degraded availability across Copilot Chat, VS Code, and other Copilot features. This impacted code generation and assistance for developers relying on that model, while other Copilot models remained available. The issue began at 2:16 PM UTC and the services were restored by 3:46 PM UTC, a total duration of approximately 1 hour and 30 minutes. A small number of user reports indicated degraded performance during the event.

GitHub's status updates confirmed the root cause as an upstream model provider issue. The Copilot component moved from up to degraded (warn) during the incident and returned to normal after remediation. The provider issued two status updates detailing the degraded availability and subsequent recovery.

GitHub experienced a service-wide degradation beginning at Dec 11, 2025 3:51 PM UTC as reports of rising request failures surfaced. The impact expanded quickly: API Requests and Actions degraded by Dec 11, 2025 4:01 PM UTC and then additional services including Copilot, Codespaces, Pages, Packages, Git Operations, Webhooks, Pull Requests, and Issues entered degraded states by Dec 11, 2025 4:11 PM UTC. Users globally reported trouble accessing repositories, running workflows, and using key features. The outage lasted approximately 2 hours and 5 minutes, with all listed components returning to normal by Dec 11, 2025 5:56 PM UTC.

GitHub Actions experienced a brief degradation when macOS jobs were routed to Ubuntu runners, impacting macOS workflow runs. The issue began around 1:34 PM UTC and the Status Page marked degraded performance for Actions at 1:36 PM UTC. The incident lasted approximately 1 hour and 20 minutes and was resolved by 2:56 PM UTC. A small number of user reports were observed during the window, including around 2:30 PM UTC.

GitHub Actions experienced a brief degradation that caused delays starting runs. The issue began at Dec 10, 2025 9:11 AM UTC when the Actions component was listed as degraded and was resolved by Dec 10, 2025 11:06 AM UTC. The GitHub Status page issued 2 updates during the incident, and a small number of user reports were received, including a report from Vienna at 10:21 AM UTC, indicating delays across workflows.

GitHub Copilot experienced degraded performance, with some users seeing Copilot-related errors and reduced autocompletion quality. The Copilot component was listed as degraded during the incident, and the issue appeared to affect Copilot features for a subset of users (for example, Copilot error messages like 400) based on user reports.

The outage began at 7:01 AM UTC and was resolved by 8:26 AM UTC, lasting roughly 1 hour and 25 minutes. GitHub posted two status updates during the incident — first indicating an investigation into degraded Copilot performance, then confirming recovery as Copilot returned to normal. The impact was limited to Copilot and did not indicate broader issues across GitHub services.