GitHub Outage History

GitHub experienced an incident where Actions run start delays affected a subset of users. The Actions component was listed as degraded during this period, causing longer startup times or failures when triggering workflows for an estimated 4% of users. The outage began on 2:21 PM UTC and was resolved by 3:46 PM UTC, lasting about 1 hour and 25 minutes.

GitHub communicated the incident through two status updates on their status page, describing the investigation and restoration of services. Limited user reports accompanied the event, indicating a partial impact rather than a global outage.

GitHub experienced degraded performance affecting core development workflows. Users reported intermittent latency and errors with Webhooks API/UI and Pull Requests, with related issues across several adjacent services (Issues, Actions, Git Operations, and Copilot Coding Agent). The incident began at Feb 9, 2026 8:16 AM UTC and persisted for several hours, during which GitHub issued eight official status updates while investigating and applying mitigations. The incident impacted six components: Pull Requests, Webhooks, Issues, Actions, Git Operations, and Copilot Coding Agent.

GitHub experienced a brief degradation impacting the Pull Requests component, causing slower PR-related actions for about 50 minutes. The incident began at Feb 6, 2026 5:51 PM UTC with Pull Requests listed as degraded. A subsequent update at Feb 6, 2026 6:06 PM UTC indicated Pull Requests was operating normally, and full recovery was confirmed by Feb 6, 2026 6:41 PM UTC. GitHub issued 3 official status updates during the incident, with the issue localized to the Pull Requests component and no broader service impact indicated.

GitHub Copilot experienced a brief period of degraded performance affecting Copilot features for users. The incident began at 11:16 AM UTC and was resolved by 12:01 PM UTC, lasting about 45 minutes. The GitHub Status page listed Copilot as degraded during the event, and two status updates were posted over the course of the incident. A small number of user reports indicated limited impact beyond Copilot functions.

GitHub Actions experienced degraded performance with delays in Runs, causing workflows to be delayed and some jobs not to queue or run as expected. Users reported webhooks not firing and Actions jobs not triggering across multiple regions. The incident began at 4:11 PM UTC and was resolved by 7:31 PM UTC. The provider issued 2 status updates during the incident, reflecting ongoing investigation and subsequent resolution. Reports spanned several regions, indicating broad geographic impact.

GitHub experienced a Copilot related incident that caused degraded performance for Copilot features across IDE integrations. Developers relying on AI-assisted coding may have encountered slower or intermittent Copilot suggestions during the event. The outage began at Feb 3, 2026 10:16 AM UTC and was resolved by Feb 3, 2026 11:01 AM UTC, lasting about 45 minutes. A large volume of user reports started around 9:45 AM UTC, indicating significant early impact before GitHub acknowledged the issue. GitHub issued 2 status updates during the incident, with the Copilot component moving from degraded to normal after the final update.

GitHub Copilot users experienced 502 errors when making Copilot requests, disrupting code completion and related features across various IDEs and interfaces. User reports came from around the globe, with activity peaking between 09:45 and 10:00 UTC and subsiding thereafter, indicating a widespread impact across multiple regions.

StatusGator flagged the incident early, with issues detected starting at Feb 3, 2026 9:04 AM UTC based on user reports before any provider updates. The outage lasted about 1 hour and 12 minutes, resolving by Feb 3, 2026 10:16 AM UTC. The event affected users globally rather than being confined to a specific region, underscoring the broad reach of the Copilot service during the incident.

GitHub experienced a multi-service outage that disrupted core developer workflows. From 7:46 PM UTC, GitHub Actions, Codespaces, Copilot, and Pages faced degraded performance or outages, causing hosted runners to queue, jobs to fail, codespaces to fail to be created or resumed, and general disruption to automated processes. Developers worldwide reported stalled workflows, unavailable environments, and intermittent page performance while the incident was ongoing.

GitHub reported a brief disruption affecting some services, with the Git Operations component showing degraded performance. Users attempting Git operations may have noticed slower responses or intermittent failures during the incident.

The incident began at Feb 2, 2026 5:36 PM UTC and was resolved by Feb 2, 2026 5:46 PM UTC, lasting about 10 minutes. The GitHub status page issued two updates describing the degraded performance and ongoing investigation, and the issue was resolved when services returned to normal.

GitHub Actions experienced degraded performance affecting the ability to start workflows. The issue spanned roughly 44 minutes, with users noticing delays in triggering and queuing Actions runs across projects. The incident began at 3:12 PM UTC and was resolved by 3:56 PM UTC.

The GitHub status page documented the timeline: an initial investigation was opened at 3:12 PM UTC and the Actions component moved to a degraded state by 3:16 PM UTC. The issue was cleared by 3:56 PM UTC, with two official status updates posted during the incident. Impact appeared limited to GitHub Actions, with no broader service disruption reported. User reports described isolated delays in workflow starts rather than a full service outage.