GitHub Outage History

GitHub Copilot users across the globe faced language model unavailability, causing Copilot to fail to generate code suggestions and other Copilot features to become unresponsive in IDEs and chat. The language model powering Copilot was unavailable for much of the day, with reports of 'Language model unavailable' and related errors affecting users in multiple regions. Impact began around 5:15 AM UTC and persisted for most of the day, with recovery by 9:47 PM UTC.

Users relying on GitHub Copilot experienced disruption as the Copilot Dashboard on the Insights tab became inaccessible. The issue appeared to affect Copilot-related services rather than the entire GitHub platform, with reports of features not loading and language-model services unavailable across multiple regions. Impact began amid early user reports around 1:45 AM UTC and expanded as updates acknowledged the Copilot dashboard issues.

GitHub’s status updates escalated the incident, first noting disruption with some GitHub services at Apr 14, 2026 2:01 AM UTC. By Apr 14, 2026 4:41 AM UTC the Copilot Dashboard on the Insights tab was identified as the affected component and mitigation efforts were underway. The issue gradually stabilized, with the status returning to normal around 6:11 AM UTC.

A brief outage affected GitHub Pages, degrading the availability of websites hosted on the Pages service. Users attempting to load Pages-hosted sites experienced failures or delays. The incident began at Apr 13, 2026 7:56 PM UTC and was mitigated by 8:31 PM UTC, with full restoration by 8:36 PM UTC as GitHub worked to ensure stability.

GitHub’s status updates indicated the Pages degradation and subsequent recovery, with officials monitoring the service to confirm stability after mitigation.

GitHub users worldwide faced intermittent performance and access issues impacting Copilot and other GitHub services. Impact began around 4:02 PM UTC per StatusGator's Early Warning Signal. GitHub acknowledged the disruption around Apr 13, 2026 4:46 PM UTC and said the root cause had been identified, with a Copilot fix being rolled out and full recovery expected in 5 to 10 minutes. StatusGator’s early warning ended around Apr 13, 2026 5:08 PM UTC as services began to recover, with subsequent updates indicating progress toward full restoration.

GitHub Copilot experienced a brief degraded performance affecting Copilot Agent Sessions (CCA/CCR). The incident began at Feb 25, 2026 4:41 PM UTC and was resolved by Feb 25, 2026 4:47 PM UTC, lasting roughly six minutes. The GitHub Status page listed Copilot as degraded during the window before returning to normal. The provider issued two status updates describing the issue and its resolution.

The GitHub code search service experienced degraded performance starting at 8:01 PM UTC and was resolved by 12:51 AM UTC, lasting about 4 hours and 50 minutes. Users attempting to search for issues or pull requests could encounter slower results or timeouts, with code search latency impacting related searches. The issue was traced to a single shard with elevated CPU usage, causing degradation across code search and later affecting searches for issues and pull requests.

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.