GitHub Outage History

GitHub Actions users relying on actions-runner-controller experienced errors from the auto-scaling APIs, causing a brief disruption for self-hosted runners. The outage lasted about 20 minutes, beginning at 4:06 PM UTC and ending at 4:26 PM UTC. A user reported issues at 3:15 PM UTC ahead of the incident being acknowledged.

GitHub's status page notes the incident started with an update posted at Jan 20, 2026 4:03 PM UTC describing API errors in actions-runner-controller and ongoing mitigation. The issue was resolved by 4:26 PM UTC. The impact appeared concentrated on workflows using the self-hosted runners managed by actions-runner-controller, with users seeing failed auto-scaling operations during the window.

GitHub faced an outage impacting core collaboration features, with Issues and Pull Requests experiencing degraded performance and intermittent errors, and the API endpoints used by automation and integrations showing degraded availability. Users reported difficulties loading issues and PR pages and creating or updating issues or PRs. The incident began at Jan 15, 2026 5:01 PM UTC as API Requests degraded, with GitHub reporting ongoing investigation and mitigation.

Over the course of about 1 hour and 55 minutes, GitHub issued seven status updates outlining the evolving impact across the affected components. API Requests returned to normal by Jan 15, 2026 5:56 PM UTC and Issues and Pull Requests recovered by around Jan 15, 2026 6:56 PM UTC. The disruptions affected 3 components and were observed by users in multiple regions, indicating a broad outage that gradually resolved.

An outage impacted four GitHub components—Pull Requests, API Requests, Issues, and Actions—causing errors and degraded performance for users trying to create or review pull requests, manage issues, or call API endpoints. The disruption began at Jan 15, 2026 5:01 PM UTC and lasted until Jan 15, 2026 6:56 PM UTC. StatusGator detected the issue at Jan 15, 2026 4:52 PM UTC, about 9 minutes before GitHub's first acknowledgment at Jan 15, 2026 5:01 PM UTC. The GitHub Status Page issued 7 updates during the incident, noting degradation across API Requests, Issues, Pull Requests, and Actions, with recovery announced progressively until all components returned to normal by Jan 15, 2026 6:56 PM UTC. User reports indicated broad, global impact, consistent with a widespread incident.

GitHub Actions experienced degraded performance due to postback delays, impacting workflow executions and related status updates. The issue began around Jan 15, 2026 2:24 PM UTC with the first status update at Jan 15, 2026 2:26 PM UTC indicating investigations into degraded performance for Actions. The outage persisted for about 1 hour and 7 minutes and was resolved by Jan 15, 2026 3:31 PM UTC.

GitHub issued two status updates during the incident outlining ongoing investigation and restoration, with user reports during the period aligning with observable delays in Actions. The event affected the Actions component and did not indicate broader GitHub service disruption.

GitHub Webhooks experienced degraded performance starting around 8:21 PM UTC, impacting webhook delivery for automation and integrations. Some users observed delays or missed events as the Webhooks component entered a degraded state. A small volume of user reports appeared before official acknowledgment.

The outage began at Jan 14, 2026 9:26 AM UTC and was resolved by Jan 14, 2026 10:56 AM UTC. GitHub Copilot's GPT-5.1 model experienced degraded performance, with users likely noticing slower or less reliable code suggestions during the incident. The Copilot component was listed as degraded, and reports from users across regions supported the occurrence of reduced Copilot responsiveness during this period.

GitHub issued two status updates as they investigated the issue and confirmed restoration of Copilot, with the service returning to normal after approximately 1 hour and 30 minutes.

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.