GitHub Outage History

The GitHub Copilot service suffered an outage that prevented all Copilot requests from being fulfilled, impacting developers relying on AI-assisted code suggestions across platforms. User reports from around the world indicated Copilot was unavailable for a period, with many users unable to receive code suggestions or complete Copilot-related actions. The incident lasted about 1 hour, beginning at 9:46 AM UTC and ending at 10:46 AM UTC.

GitHub documented the incident on its status page with three updates: an initial investigation as Copilot failures at Jan 13, 2026 9:46 AM UTC, a note of degraded performance at Jan 13, 2026 10:16 AM UTC, and a final restoration at Jan 13, 2026 10:46 AM UTC.

GitHub Copilot experienced a service disruption that blocked Copilot requests and degraded performance for many users. The outage began at Jan 13, 2026 9:46 AM UTC when GitHub reported receiving no requests to Copilot, signaling a widespread interruption of Copilot services. StatusGator detected an Early Warning Signal at Jan 13, 2026 9:26 AM UTC, about 20 minutes before GitHub’s official acknowledgment, highlighting initial issues before formal page updates. Users across regions reported Copilot failures and missing code completions in editors and IDEs during the early phase of the incident.

GitHub Actions experienced a brief degradation in performance, affecting GitHub Actions workflows and related automation. The incident began at Jan 12, 2026 10:06 AM UTC when the Actions component was listed as degraded, with GitHub reporting ongoing investigation. The outage lasted about 15 minutes, with the Actions component returning to normal by Jan 12, 2026 10:21 AM UTC. GitHub posted two updates during the incident describing the degradation and subsequent recovery. The impact was limited to the Actions component and did not indicate broader issues across other GitHub services.

The GitHub Copilot Grok Code Fast 1 model experienced degraded availability across Copilot Chat, VS Code, and other Copilot products due to an upstream model provider issue. The outage began at Jan 8, 2026 12:46 AM UTC and was resolved by Jan 8, 2026 1:36 AM UTC, lasting roughly 50 minutes. Other Copilot models remained available and functioning. The GitHub Status page posted two updates during the incident, noting the degraded state and the upstream provider issue and later confirming service restoration.

GitHub Copilot users experienced missing Copilot models across VSCode and other Copilot-enabled experiences, resulting in degraded access to Copilot features. The outage began at Jan 7, 2026 6:36 PM UTC and was resolved by Jan 7, 2026 9:11 PM UTC, lasting about 2 hours and 35 minutes. Users reported that Copilot models did not load or appear as expected.

GitHub issued two status updates during the incident, noting the investigation into the cause and efforts to restore access to Copilot models. The issue affected the Copilot component across VSCode and other Copilot-enabled workflows, and the disruption appeared limited to model availability rather than a broader service outage, based on the public updates.

GitHub experienced a brief disruption affecting artifact downloads from Actions workflows via the web interface. The outage began at 4:46 PM UTC and was resolved by 5:06 PM UTC, lasting about 20 minutes. The impact was isolated to the Actions component, with no broader GitHub services affected. The incident prompted two official status updates from GitHub during the window as investigators worked on a fix.

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.