GitHub Outage History

A brief outage affected GitHub Actions when starting runs, causing delays for workflows. The incident began around 3:12 PM UTC with the status page noting an investigation at 3:16 PM UTC and listing the Actions component as degraded. The issue impacted the start of Actions workflows across affected jobs. The provider posted two updates during the incident, and normal service was restored by 3:56 PM UTC, for an outage duration of about 40 minutes. User reports were limited, indicating a relatively small portion of users were affected.

GitHub experienced degraded performance in the Issues feature for a brief period, potentially slowing down creating, viewing, or managing issues for users. The disruption began around 2:23 PM UTC and was resolved by 2:31 PM UTC, lasting roughly 8 minutes. User reports were observed during this window, including some from the Netherlands indicating slower UI responses.

GitHub's status page documented the incident with updates: an initial note at 2:23 PM UTC stating degraded performance and ongoing investigation, and a follow-up at 2:26 PM UTC signaling the issue as a partial outage before returning to normal by 2:31 PM UTC. The incident involved the Issues component and caused a brief, temporary impact before full recovery.

GitHub Copilot Chat experienced a brief degradation that impacted Grok Code Fast 1. The incident began around 11:33 AM UTC, with the status page noting Investigation at 11:36 AM UTC. The Copilot component returned to normal by 12:41 PM UTC, lasting about 1 hour 8 minutes. The GitHub Status page published two updates during the incident, and user reports were limited.

GitHub Actions experienced a brief period of degraded performance affecting run start times. The Actions component moved to a degraded state at around 7:51 PM UTC, after GitHub noted an investigation into reports of degraded performance for Actions at Jan 20, 2026 7:49 PM UTC. The disruption lasted roughly 22 minutes and was resolved by 8:11 PM UTC. A small number of user reports described workflow start delays, and the impact was limited to GitHub Actions.

GitHub's status updates documented the incident. The provider posted two official updates during the event, keeping affected users informed. The outage did not affect GitHub services beyond Actions, and status was restored to normal by the end of the window.

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.