GitHub Outage History

An outage affected multiple GitHub services, causing degraded performance and partial outages for users. Issues and Webhooks were among the first impacted, with downstream effects on Git Operations, Actions, Packages, Pull Requests, Pages, and Codespaces. In practice, users experienced failed PR reviews (including errors like invalid JSON), automation slowdowns, and slower page loads across the platform.

Status updates tracked the progression: the incident began at 3:46 PM UTC with degraded performance for Issues and Webhooks, followed by Git Operations degradation at 3:51 PM UTC and broader impact to Actions and Packages at 3:57 PM UTC. Pull Requests entered a degraded state at 4:01 PM UTC, and Pages and Codespaces showed issues by 4:06 PM UTC. The platform began recovering in stages, with Git Operations returning to normal by 4:26 PM UTC and full recovery by 4:41 PM UTC.

From 2:01 PM UTC, GitHub faced an outage affecting GitHub Actions with hosted ubuntu-latest and ubuntu-24.02, causing high wait times and job start delays. Other hosted labels and self-hosted runners were not affected initially. The disruption extended to pull request data as Elasticsearch indexing did not reflect all indexed documents, leading to incomplete PR listings and search results on some pages. Users across regions reported timeouts and slow builds during the peak of the incident.

GitHub rolled out mitigations to unblock Actions and began reindexing Elasticsearch indexes. Data remained intact and pages not relying on Elasticsearch stayed usable through the recovery period. Over the following days, indexing progressed and most data and PR listings were restored; by 4:16 AM UTC, the Pull Requests component was up and the incident was substantially resolved.

Impact began at 4:31 PM UTC as GitHub reported degraded search, spreading to core workflows and features. Users experienced workflow run failures, projects failing to load, and timeouts when searching, with pull requests, issues, and packages also affected. The degradation appeared across several components and was noticeable to users around the afternoon and evening, leading to broader service disruption for many developers and teams.

By 7:51 PM UTC, GitHub indicated the root cause was an excessive load on ElasticSearch clusters and disabled the offending source, with signs of recovery soon after. The issue was reframed as having been mitigated by 9:36 PM UTC, though monitoring continued to ensure stability. Recovery culminated with services returning toward normal by 10:51 PM UTC.

Impact began at Apr 24, 2026 7:06 PM UTC when GitHub flagged delays with Actions Jobs for Larger Runners using VNet Injection in the East US region. The issue led to degraded performance for workflows and related services, with updates noting ongoing investigation and a broader public impact tied to Azure East US workloads. Users across regions reported problems ranging from difficulty connecting to Copilot to language model availability issues, indicating the incident affected developer tooling and CI workflows in the affected region.

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.

StatusGator detected issues at 2:26 PM UTC, about 14 minutes 56 seconds before GitHub acknowledged the problem at Apr 23, 2026 2:41 PM UTC. Users began reporting degraded loading of GitHub pages and delays in Actions runs as the incident expanded to cover Actions, Codespaces, Copilot and Packages. Impact was global, with users across many regions reporting errors and slow page loads; the outage affected github.com and related services starting in the early afternoon and persisted into the early evening.

GitHub's status updates described an ongoing investigation into errors and degraded performance across Actions, Codespaces, Copilot and Packages. The degradation was mitigated by 3:06 PM UTC and services began returning to normal, with full recovery by 3:21 PM UTC.

Reports surged around 2:30 PM UTC as users worldwide experienced issues, indicating a broad, global impact rather than a localized outage. The incident lasted roughly an hour before stability returned.

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.