GitHub Outage History

Users experienced degraded performance with GitHub Pull Requests starting around 7:51 PM UTC as the status page flagged an incident for Pull Requests. A regression in the merge queue behavior affecting squash merges or rebases disrupted PR processing, with some merges possibly occurring incorrectly during the window from 4:05 PM UTC to 8:43 PM UTC UTC.

By 8:56 PM UTC GitHub indicated Pull Requests was operating normally again and that the root cause had been identified with a revert in progress. The service returned to up by 9:46 PM UTC. The incident appears to have affected users attempting merges or squash/rebase operations during the impacted period, with the disruption most evident in merge outcomes during the window above.

GitHub experienced a brief disruption where users could not start Claude and Codex agent tasks from the web. The disruption began at 7:31 PM UTC, as the service entered a degraded state for web-initiated Claude and Codex tasks. Engineers identified the root cause and began mitigation by 7:36 PM UTC. The service returned to normal by 7:46 PM UTC. A single user report was logged during the window at 7:30 PM UTC, indicating limited user impact. The issue appeared limited to the web-based startup flow for Claude and Codex agents, with no broader GitHub services affected.

An outage began at 4:16 PM UTC when GitHub reported degraded availability for Copilot and Webhooks. The issue quickly affected Copilot models and related automation, with users experiencing Copilot models unavailable and some Webhooks-driven workflows failing. Reports came from users in multiple regions, indicating a broad impact on development workflows that rely on Copilot and event-driven automation.

GitHub's status updates showed a root cause identified by 4:56 PM UTC and mitigation underway. By 5:06 PM UTC many services were mitigated and were validating the remainder. Copilot began recovering, and Actions and Webhooks were restored in sequence, with Webhooks operating normally by 5:11 PM UTC and a full recovery by 5:31 PM UTC. The incident produced noticeable disruption for developers relying on Copilot and automation, with users reporting degraded or unavailable services for about an hour before operations returned to normal.

GitHub experienced a global outage that disrupted core developer workflows and web access. Users reported errors loading GitHub.com pages, login failures, and workflows not triggering as Actions, Codespaces, Copilot, and Packages encountered degraded performance across regions. The incident began at Apr 23, 2026 2:26 PM UTC with a surge in reports around 2:30 PM UTC indicating broad impact. GitHub acknowledged the issue and began investigating at 2:41 PM UTC. StatusGator detected the issue at Apr 23, 2026 2:26 PM UTC, about 15 minutes before the official acknowledgment.

Impact began around Apr 22, 2026 7:56 PM UTC with degraded performance across GitHub services, most notably in GitHub Issues. Users attempting to work with issues and related workflows experienced slower responses and some functionality not behaving as expected. In PR workflows, Copilot @-mentions were not being processed by the Copilot Cloud Agent, affecting automation and guidance for contributors.

By Apr 22, 2026 10:11 PM UTC a root cause was identified and a fix started deployment to address Copilot Coding Agent and Issues. The team continued remediation through the evening, and normal operation for the Issues component was restored by Apr 22, 2026 10:46 PM UTC with services returning to standard performance.

GitHub Copilot Chat and Copilot Cloud Agent on github.com experienced a broad outage starting around 3:36 PM UTC. Users reported Copilot chats failing to load, inability to start new chats, and errors when invoking Copilot tasks. StatusGator recorded an Early Warning Signal, with issues detected at Apr 22, 2026 3:15 PM UTC and the signal ending at 5:52 PM UTC, indicating the problem was known to users roughly 21 minutes before GitHub acknowledged it. The disruption appeared globally, with reports spanning Europe, the Americas, and Asia, and persisted for most of the afternoon.

GitHub's status updates framed the incident as a disruption with Copilot chat and Copilot Coding Agent, with ongoing mitigation. By around 6:06 PM UTC engineers reported progress mitigating Copilot cloud agent and chat on github.com, and the outage was resolved later that evening with Copilot Chat and Cloud Agent returning to normal by 7:21 PM UTC.

Users worldwide experienced delays in GitHub Projects, with changes to projects not reflecting immediately. The disruption began at Apr 21, 2026 3:06 PM UTC and led to a backlog of updates while GitHub investigated and implemented mitigations, causing delays in project changes and related workflow updates.

GitHub communicated an ongoing investigation and deployed fixes to relieve the processing backlog. As the team worked to clear pending events and restore normal timing, recovery progressed and the status was updated to up at Apr 22, 2026 1:26 AM UTC as the backlog cleared and updates resumed typical timing; some residual delays may have persisted during the transition.

Developers relying on GitHub's code scanning and code quality checks for pull requests faced degraded performance beginning 1:31 PM UTC as GitHub flagged a partial degradation in code scanning defaults and code quality features. PR scans and quality analyses were not reliably triggered on new pull requests, impacting typical review workflows. User reports circulated through the afternoon, signaling a broad impact on PR-related tooling and project-management signals.

Mitigations progressed over the next several hours. The incident escalated to a more disruptive state at 2:01 PM UTC, with the root cause identified and mitigations being deployed. By 4:21 PM UTC, code scanning and Code Quality triggers were back up and running, but developers were warned that PRs created before or during the incident might require a new push to trigger analyses, and that some new issues were not showing on project boards. Deployments and remediation continued through the evening, with the situation described as mitigated by 6:21 PM UTC and ongoing monitoring. A note at 3:11 AM UTC indicated that issues linked to projects during the incident could take roughly three more hours to render while a re-index completed, and stability was rechecked by 4:21 AM UTC before final recovery. The service returned to up status by 5:06 AM UTC.

GitHub.com users faced slow page loads and failed requests as roughly 10% of web traffic was affected. The disruption began around Apr 17, 2026 2:18 PM UTC and manifested as slow responses and errors across core web endpoints, with reports of timeouts when loading pages or performing actions like repository access. A surge in user reports mid-afternoon UTC reflected the growing impact. StatusGator detected the issue about 43 minutes before GitHub publicly acknowledged it. The root of the disruption was traced to a problematic component, which GitHub proceeded to isolate as part of mitigation.

Users of GitHub Codespaces faced degraded performance when creating new Codespaces or starting existing ones from the VS Code editor, with SSH connections remaining unaffected. The disruption began around 3:11 PM UTC and rapidly escalated to a broader outage, affecting about 70% of Codespaces by 3:51 PM UTC. Reports described sessions failing to start and, in some cases, complete outages for parts of Codespaces users, including observations from Europe and North America.