GitHub Outage History

GitHub reported a short outage affecting Larger Hosted Runners, causing extended job start delays and longer queues for some larger runner jobs. The incident began on 8:01 PM UTC and was resolved by 8:41 PM UTC. The GitHub Status Page posted three updates during the incident, including an initial notice of degraded performance, a follow-up with ongoing investigation and improving queue times, and a final confirmation that the service had recovered.

GitHub Copilot's GPT-5.1 Codex model experienced degraded availability across Copilot Chat, VS Code, and other Copilot products due to an upstream model provider issue. The outage began when the Copilot component entered a degraded state at 10:06 AM UTC and lasted about 1 hour and 40 minutes. During the incident, GPT-5.1 Codex performance was limited and Copilot-related features may have been affected across IDE integrations. The issue was acknowledged by GitHub and monitored as the provider worked with the upstream model provider to resolve the problem.

The GitHub Status page issued four updates during the incident. By 11:21 AM UTC the upstream issues were resolved and GPT-5.1 Codex was available again in Copilot Chat and across IDE integrations (VSCode, Visual Studio, JetBrains). The Copilot component moved back to normal operation by 11:46 AM UTC, and GitHub stated that monitoring would continue to ensure stability.

GitHub experienced degraded performance in its merge queue, impacting the Pull Requests workflow and causing slowdowns in PR merges and related checks. Users attempting to merge PRs or move PRs through CI checks may have faced longer processing times during the incident. The outage began at 6:26 PM UTC and lasted about 55 minutes, until 7:21 PM UTC. A small number of user reports appeared around 5:30 PM UTC, indicating early visibility before official acknowledgment. During the incident, GitHub issued 3 status updates to communicate investigation progress and resolution. The issue was resolved and normal PR merge throughput returned to baseline by 7:21 PM UTC.

GitHub experienced intermittent authentication failures affecting token-based workflows, impacting GitHub App server to server tokens, GitHub Actions authentication tokens, and git operations. Some API requests could fail intermittently, and a subset of users reported issues with workflows such as Codespaces. This was not a full service outage, but authentication across multiple paths was degraded during the incident.

GitHub reported a brief disruption affecting file upload functionality across a subset of services. The issue began at 10:36 PM UTC and was resolved by 11:01 PM UTC, lasting about 25 minutes. GitHub posted two status updates during the incident to acknowledge the disruption and communicate that teams were investigating, with normal operation returning after the incident window. User reports during the window indicated problems with uploading files, suggesting the impact was limited to specific workflows rather than a full service outage.

The outage began at Feb 12, 2026 6:36 PM UTC with GitHub logging degraded performance affecting some services. Users encountered slower responses and intermittent issues as the team investigated. The incident was resolved by Feb 12, 2026 8:36 PM UTC, with services returning to normal after about 2 hours.

GitHub issued 2 official status updates during the incident. User reports came from locations including Boston, USA, and Le Vaudreuil, France, indicating a localized degradation reported from multiple regions.

GitHub Copilot completions and inline code suggestions experienced intermittent disruption, with degraded availability in certain regions. The outage began at Feb 12, 2026 2:11 PM UTC and was resolved by Feb 12, 2026 4:51 PM UTC, lasting approximately 2 hours and 40 minutes, impacting developers relying on AI-assisted coding. The incident prompted two status updates describing the regional impact and ongoing mitigation efforts.

GitHub experienced a brief outage affecting downloads of repository archives that include Git LFS objects. Users attempting to download large repositories or archives containing LFS objects may have encountered failures or slowdowns. The incident began at 10:42 AM UTC and was resolved by 11:16 AM UTC, lasting about 34 minutes. The disruption was limited to the repository archive download path and did not indicate a broader service outage.

The GitHub Codespaces outage began at 7:56 AM UTC, with degraded availability for the Codespaces component. Users attempting to create or access Codespaces environments faced failures or slow performance, disrupting development workflows for approximately two hours. The incident was resolved by 9:56 AM UTC.

GitHub issued three official status updates during the incident, documenting the progression from degraded availability to degraded performance and eventual recovery. The Codespaces component returned to normal after the final update, with services restored by 9:56 AM UTC.

GitHub experienced degraded performance affecting some services beginning at 7:01 PM UTC. Users reported slower response times and intermittent access issues across a subset of GitHub features, indicating a partial outage rather than a full shutdown. The issue lasted for about 6 hours and was resolved by 1:01 AM UTC.

The GitHub Status Page issued 2 updates during the incident as investigators worked to restore normal operations. User reports originated from Ottawa, Canada and Kowloon, Hong Kong, suggesting the impact was geographically distributed rather than isolated. While overall volume of reports was low, the timing aligns with the degradation window, highlighting a broad user experience impact.