GitHub Outage History

Users across the globe faced Copilot login and code-completion problems, limiting access to Copilot features in VSCode and related Copilot API endpoints. The first user reports appeared around 10:15 PM UTC, and the issue quickly drew a large volume of feedback as it progressed through the night. StatusGator flagged an Early Warning Signal starting at May 14, 2026 10:40 PM UTC, indicating user reports preceded any official acknowledgment on GitHub's status page. The early warning remained active until 5:33 AM UTC.

As the situation evolved, GitHub's official status updates are not reflected in the provided data; the incident centered on Copilot login and API access disruptions, with reports tapering off in the early morning hours as services began to recover.

GitHub Copilot users experienced an outage starting around 1:44 AM UTC, with login failures and token delivery issues across IDEs like VS Code. The disruption lasted about 1 hour 37 minutes and was largely resolved by 3:21 AM UTC. In practice, developers across multiple regions reported Copilot being unavailable, hindering code suggestions and automated token-based sign-in workflows.

StatusGator detected the issue at May 14, 2026 1:44 AM UTC, ahead of any official acknowledgment. There were no official updates on GitHub's Copilot status page during the incident, even as user reports surged around 2:15 AM UTC from places including Brazil, the United States, and Taiwan, indicating a broader impact. Access began to recover by 3:21 AM UTC.

GitHub faced an incident centered on CodeQL, the code analysis engine behind Code Scanning. On May 13, 2026 2:41 PM UTC, GitHub flagged an incident with reported degraded performance across some services. Users worldwide began experiencing delayed or incomplete code scanning results as CodeQL processing slowed. Some reports also described Copilot errors and CodeSpaces loading issues, illustrating broader impact beyond CodeQL alone.

Engineering teams applied a mitigation to increase processing capacity by 3:01 PM UTC, with monitoring ongoing to confirm full recovery. The service was observed returning to normal around 3:31 PM UTC. The incident affected CodeQL and Code Scanning workflows globally, with user reports from London, Cairo, Accra, Groenlo, and Brooklyn reflecting the broad geographic reach.

Impact began around 2:41 PM UTC as GitHub flagged degraded performance for CodeQL and Actions. Users saw actions not starting, jobs stuck in pending, or timing out, and Webhooks also experienced degraded performance.

Over the next couple of hours, GitHub engineering worked to scale out a queuing service at the heart of the delays. By 4:21 PM UTC engineers reported early signs of recovery for some services and continued work on the rest. Webhooks fully recovered by 4:31 PM UTC, CodeQL had fully recovered by 5:01 PM UTC, and overall service readiness followed with the final update showing all systems up by 5:46 PM UTC.

The incident began around 2:26 PM UTC, when GitHub listed Git Operations as degraded due to high error rates affecting typical Git tasks. Developers likely faced failed or slow pushes, pulls, and clones as the issue unfolded.

GitHub acknowledged the degradation and traced the issue in status updates, with the Git Operations component returning to normal by 2:36 PM UTC. The event generated a noticeable uptick in user reports during the peak, but the impact appeared confined to Git operations rather than broader GitHub services.

GitHub experienced a partial outage that disrupted pull request workflows tied to Copilot code review. The incident began at 5:06 AM UTC when CCR and CCA failed to start for PR comments, hindering reviewers' ability to engage with PRs and limiting Copilot-assisted review features. The effects were felt across multiple regions, with user reports describing difficulties around PR comments, attempted auto-merges, and review cues during the height of the incident.

By 6:56 AM UTC, GitHub indicated recovery as Copilot code review and cloud agents began starting up again for pull requests, with ongoing monitoring for full restoration. The outage lasted roughly one hour and fifty minutes, after which features returned to normal as services resumed. The disruption manifested as delayed or missing Copilot review assistance and PR tooling responsiveness while updates from GitHub guided the path to full recovery.

GitHub’s Pull Requests feature experienced degraded availability, with users reporting difficulties creating new PR threads and adding comments to specific lines and files. Top-level comments on pull requests remained usable, and core PR actions such as opening and merging PRs continued to function. The disruption began at 3:26 PM UTC and generated a global signal as the afternoon progressed, with a notable volume of user reports indicating widespread impact.

An outage briefly disrupted Copilot Cloud Agent sessions on GitHub, preventing users from starting Copilot Cloud Agent sessions or viewing them. The disruption began at 11:26 AM UTC and affected early activity as users attempted Copilot workflows.

GitHub confirmed the disruption and the service was restored by 12:01 PM UTC, after roughly 35 minutes. The issue appeared limited to Copilot Cloud Agent session initiation and viewing, with other GitHub features not indicated as affected. User reports in the late morning aligned with the impact window, before recovery.

The GitHub Actions service experienced degraded availability as Ubuntu standard hosted runners encountered long queues and slow job execution. The incident began at 7:21 AM UTC with early reports of delays and ongoing investigations by the Actions team.

In East US, GitHub Actions experienced degraded performance with elevated queue times and failures impacting a portion of runs. Hosted Runners in the region, including those with private networking, could fail over to a different Azure region to mitigate the issue. Separately, SSH-based Git operations saw elevated latency and failures between 2:00 PM UTC and 4:10 PM UTC UTC, while HTTP-based operations were largely unaffected.

GitHub and its compute partner pushed mitigations and ongoing recovery steps through the afternoon. A mitigation for long queue times was applied around 3:56 PM UTC, with signs of recovery beginning by 4:36 PM UTC as standard Hosted Runners improved and the SSH-related impact was contained. By 6:36 PM UTC the degradation had been mitigated and services were monitored for stability, marking the return toward normal operation.