GitHub Outage History

GitHub Copilot experienced degraded availability affecting Copilot Chat, VS Code and other Copilot products due to an upstream model provider issue. Other Copilot models remained available. The incident began at Feb 23, 2026 3:01 PM UTC and lasted until Feb 23, 2026 5:06 PM UTC, with users reporting delays in job processing and slower queues across Copilot features.

The provider issued five official updates during the incident. Copilot was reported as operating normally by 4:01 PM UTC, and Actions showed degraded performance starting at 4:21 PM UTC before returning to normal by 5:06 PM UTC. The situation prompted heightened user reports across regions but many services remained accessible overall.

The incident affected GitHub's Larger Hosted Runners, causing extended job start delays and longer queue times for larger runner jobs. This degraded workflow performance for users attempting to start larger builds and tests. The outage began at 8:01 PM UTC and was resolved by 8:41 PM UTC, lasting about 40 minutes. GitHub's status page issued three updates during the incident, including the initial degradation alert, ongoing investigation notes, and the final progress update as queue times improved.

GitHub Copilot experienced degraded availability for the GPT-5.1 Codex model, impacting Copilot Chat, VS Code and other Copilot features. The incident began at 10:06 AM UTC due to an upstream model provider issue and affected Copilot functionality for about 1 hour and 40 minutes, with recovery completed by 11:46 AM UTC. A status update at 11:21 AM UTC indicated the upstream issue had been resolved and GPT-5.1 Codex was available again across Copilot Chat and IDE integrations (VSCode, Visual Studio, JetBrains). The Copilot component remained degraded until 11:46 AM UTC when it returned to up.

GitHub experienced degraded performance in the merge queue, impacting Pull Requests and related merge workflows. Users may have seen slower PR merges and delays in checks tied to PRs. The incident began at 6:26 PM UTC and was resolved by 7:21 PM UTC, lasting about 55 minutes.

GitHub's status page documented the incident with three updates: the initial notice at 18:26 UTC indicating degraded performance in the merge queue, a follow-up at 18:31 UTC confirming continued investigation into merge queue issues, and a final update at 19:21 UTC stating the issue was resolved and the merge queue returned to normal.

The impact appeared limited to the Pull Requests component; there is no indication of broader service disruption to other GitHub features during this window.

GitHub experienced intermittent authentication failures affecting GitHub App server-to-server tokens, GitHub Actions authentication tokens, and git operations. Some customers may have encountered intermittent API request failures when using these tokens, impacting automated workflows, CI/CD pipelines, and code operations that rely on token-based authentication. The incident began at Feb 17, 2026 5:51 PM UTC and lasted for about 1 hour and 15 minutes, with recovery observed by the final update at 7:06 PM UTC. Affected components included Actions and Git Operations.

An outage briefly affected GitHub file upload services, impacting users attempting to upload files. The disruption began at 10:36 PM UTC and lasted about 25 minutes, with services restored by 11:01 PM UTC. GitHub posted two status updates describing the disruption and the subsequent restoration. Early user reports indicated the issue started before the official acknowledgment, but the impact was limited to file upload workflows rather than a full platform outage.

GitHub experienced degraded performance impacting a subset of services. Users reported slower operation and intermittent issues across affected features. The incident began at Feb 12, 2026 6:36 PM UTC when the GitHub status page flagged a disruption with some services and indicated investigators were looking into reports of impacted performance. The outage lasted about 2 hours and was resolved by Feb 12, 2026 8:36 PM UTC.

During the incident, GitHub issued 2 status updates to communicate the situation and recovery. User reports came from multiple regions, including Boston, United States, and Le Vaudreuil, France, suggesting international reach. While not all GitHub services were affected, the degradation disrupted workflows for affected users during the window.

GitHub Copilot completions and inline suggestions experienced degraded availability in some regions. Users could see intermittent or missing Copilot suggestions during the incident. The outage began on 2:11 PM UTC and was resolved by 4:51 PM UTC, lasting approximately 2 hours and 40 minutes. The issue affected Copilot features across multiple regions.

GitHub issued two status updates during the incident, describing intermittent disruption and work to resolve the issue. The service returned to normal following the final update as Copilot features stabilized.

The GitHub service experienced a brief outage that prevented users from downloading repository archives containing Git LFS objects. The disruption began at Feb 12, 2026 10:42 AM UTC and was resolved by Feb 12, 2026 11:16 AM UTC, lasting about 34 minutes. User reports were present around 9:30 AM UTC prior to the incident, indicating some early visibility from the community. The impact appeared limited to archival downloads rather than a full platform outage.

GitHub’s status page published two official updates during the incident, acknowledging the disruption and that engineers were investigating, followed by confirmation of restoration. The outage primarily affected attempts to download archives with Git LFS objects rather than indicating a broader service failure.

The GitHub Codespaces outage began at Feb 12, 2026 7:56 AM UTC with degraded availability across the Codespaces environment. The issue escalated to degraded performance, and by Feb 12, 2026 9:46 AM UTC the status page listed Codespaces as degraded while teams continued to investigate. The outage lasted about 2 hours, ending with a recovery around Feb 12, 2026 9:56 AM UTC.

GitHub issued three status updates during the incident to communicate the progression: the initial notification of investigation, a follow-up noting degraded performance, and the final recovery confirmation. The disruption affected the Codespaces component and impacted users worldwide, with reported access and usage issues across multiple regions.