GitHub Outage History

The incident began at 3:31 PM UTC with degraded GraphQL API latency and a brief Copilot impact. Copilot degraded from 3:31 PM UTC to 3:51 PM UTC, while API Requests remained degraded and then returned to normal later in the incident. The outage lasted about 1 hour and 45 minutes, with API Requests fully recovered by 5:16 PM UTC. The GitHub Status page published three updates during the incident detailing investigation and recovery progress. Users reported slower GraphQL responses and, in at least one case, Copilot displaying an out-of-credits message.

The GitHub Copilot feature experienced failures as requests could not be processed due to an unsupported API version. The issue began at 1:54 AM UTC and affected Copilot usage globally, with error messages indicating the API version is no longer supported. Users reported Copilot errors and related failures across multiple regions, reflecting a broad impact on how Copilot interacted with GitHub services. The incident was observed through user reports rather than official status updates.

GitHub experienced degraded performance affecting Pull Requests and related workflows. The incident began at 3:11 PM UTC when GitHub flagged a degradation in Pull Requests and began investigating. The issue was resolved by 4:01 PM UTC with the Pull Requests component returning to normal after about 50 minutes. GitHub issued two status updates during the incident.

User reports described issues across regions, including Codespaces not working and 403 errors in Actions uploads, plus an occasional page loading error. Reports came from multiple regions such as North America, Europe, and Asia, indicating a broader but not global disruption. Activity patterns show a late-day surge, with the most reports around 15:30 UTC, aligning with the final stages of the incident.

The outage began on Feb 9, 2026 3:56 PM UTC with widespread delays in notification delivery and degraded performance across core GitHub services. Users experienced slower PR reviews and issues workflows as the problem expanded to additional components, including Actions, Webhooks, Pages, Git Operations, Packages, Codespaces, and Copilot policy propagation. The incident disrupted many common workflows for hours, with reported impact across multiple regions and services. The outage lasted roughly 18 hours and began to show recovery only after Feb 10, 2026 10:01 AM UTC as the situation gradually stabilized and affected components returned to normal.

GitHub experienced an incident affecting Actions run start times, causing delays for a portion of users. The issue began at Feb 9, 2026 2:21 PM UTC and was resolved by Feb 9, 2026 3:46 PM UTC, lasting about 1 hour and 25 minutes. Approximately 4% of users were affected, with two user reports around 2:30 PM UTC.

GitHub's status page documented the incident, with the Actions component moving from warn to up after two official updates. The event was a brief, targeted degradation affecting Actions run starts rather than a broader outage.

GitHub experienced degraded performance across multiple services, including the Webhooks API and UI, and core development workflows like Pull Requests. Users reported intermittent latency and errors when triggering webhooks, reviewing PRs, and interacting with the UI. The incident began on 8:16 AM UTC and lasted about 4 hours, with gradual improvements leading to full recovery. The issue affected 5 components: Pull Requests, Webhooks, Issues, Actions, and Git Operations.

The GitHub Status page posted 8 updates over the course of the incident, documenting the degradation, ongoing investigation, and eventual restoration. The updates show a progression from initial latency and errors to a staged return to normal across affected services. User reports were limited but included problems with PR reviews, webhook delays, and UI responsiveness. By the final update at 12:16 PM UTC, affected services had returned to normal operation.

GitHub reported degraded performance in the Pull Requests component starting at 5:51 PM UTC and lasting about 50 minutes, with recovery by 6:41 PM UTC. Users may have experienced slower PR creation and reviews, along with intermittent loading of PR-related pages. GitHub issued three status updates during the incident, noting the degraded state, confirming return to normal operation, and marking the issue as resolved. The impact appeared limited to Pull Requests and did not indicate a wider service disruption across GitHub.

GitHub Copilot experienced degraded performance starting at 11:16 AM UTC and was resolved by 12:01 PM UTC, lasting about 45 minutes. The Copilot component appeared degraded on GitHub's status page, and GitHub issued 2 official updates during the incident. User reports were limited, indicating only a small subset of users were affected. No root cause was disclosed in the updates, and Copilot services returned to normal after the incident.

The GitHub Actions subsystem experienced degraded performance centered on the Actions Runs UI. The outage began at Feb 3, 2026 4:11 PM UTC and lasted for about 3 hours and 20 minutes, until Feb 3, 2026 7:31 PM UTC when the status returned to normal. Users reported slow UI updates and intermittent issues starting workflows, with some noting that actions did not trigger or queue as expected.

GitHub communicated via the status page, noting delays in UI updates for Actions Runs and that they were investigating degraded performance. The incident affected the Actions component and was tracked with 2 official status updates before resolution. A large volume of user reports during the window indicated broad impact across regions, with symptoms including actions not firing, not queuing, and related workflow delays. There was no Early Warning Signal.

Users began reporting degraded Copilot performance starting at 9:45 AM UTC. The Copilot component was listed as degraded (warn) on GitHub Status at Feb 3, 2026 10:16 AM UTC with the update: 'Incident with Copilot' and 'We are investigating reports of degraded performance for Copilot.' The incident affected Copilot features for many users and lasted until Copilot returned to normal at Feb 3, 2026 11:01 AM UTC.

GitHub issued two status updates during the incident to document the investigation and resolution. With a large volume of user reports across multiple locations, Copilot usage was impacted for a period before full service restoration.