GitHub is having issues now

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Update - We've found the issue and are working on deploying a solution to get Codex agent runs working again.

Update - Copilot Cloud Agent (CCA) jobs using the Codex agent are failing after starting. To avoid this issue, please choose a different agent. We are investigating the cause and working towards remediation

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Update - We are investigating reports of degraded performance for Larger Runners with vnet injection in East US and we are working with our service provider on mitigation.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations. PRs merged via merge queue using the squash merge method produced incorrect merge commits when the merge group contained more than one PR. In affected cases, changes from previously merged PRs and prior commits were inadvertently reverted by subsequent merges.

Update - We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC.

Update - Pull Requests is operating normally.

Update - We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.

Investigating - We are investigating reports of degraded performance for Pull Requests

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Update - We have identified the root cause of the issue and are working on mitigation.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Update - Webhooks is operating normally.

Update - Many services are mitigated and are validating the remaining services.

Update - The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.

Update - We have identified the root problem and are working on mitigation.

Update - Actions is experiencing degraded performance. We are continuing to investigate.

Update - We are investigating multiple unavailable services.

Investigating - We are investigating reports of degraded availability for Copilot and Webhooks

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Monitoring - The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.

Update - A mitigation was applied and services have recovered.  Actions is working through queued work before fully recovering.

Update - Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

Update - Copilot is experiencing degraded performance. We are continuing to investigate.

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.

Update - Packages is experiencing degraded performance. We are continuing to investigate.

Investigating - We are investigating reports of degraded performance for Actions

Resolved - On April 22, 2026, between 09:00 UTC and 22:05 UTC, the Copilot coding agent and pull request comment event processing were degraded. During this period, approximately 0.5% of total pull request and issue comments mentioned @copilot (~23,000 invocations), explicitly requested work from the Copilot coding agent but were not acted upon.

Update - We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

Update - We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.

Update - Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

Update - Issues is experiencing degraded performance. We are continuing to investigate.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Update - Copilot cloud agent and chat are mitigated for github.com.

Update - We are now seeing recovery for Copilot cloud agent.

Update - Mitigation is progressing for Copilot chat and cloud agent recovery.

Update - Mitigation is progressing for Copilot chat and cloud agent.

Update - We continue to work on mitigation for Copilot chat and cloud agent.

Update - We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Update - The issue remains mitigated. Users may still experience small delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately two hours.

Update - The issue remains mitigated. Users may still experience delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately three hours.

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Update - Recovery from the delays affecting GitHub Projects continues to progress. We have deployed additional mitigations that are accelerating processing of the backlog. Users may still experience delays where changes to projects are not reflected immediately. We expect full recovery within approximately six hours.

Update - The queues are continuing to decrease and we are working to accelerate the rate of processing through the queues.

Update - The mitigation is deployed and we are seeing recorvery in the queues and will provide an update as to when full recovery will be realized.

Update - We are deploying a fix to relieve the queue of delayed data. Some users may still experience delays with GitHub Projects where changes are not reflected immediately as remaining backlogs are processed.

Update - We continue to investigate delays with GitHub Projects where changes may not be reflected immediately. Our team has identified the cause and applied mitigations to address the issue. We are seeing initial signs of recovery, though some delays may persist as the system works through a backlog of pending updates.

Update - We are investigating reports of delays with GitHub Projects. Users may notice that changes made to projects are not reflected immediately. Our team has identified the source of the delays and is actively working to resolve the issue.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - On April 20, 2026 between 10:28 UTC and 15:04 UTC GitHub experienced degraded service for code scanning default setup, code quality, and project boards. Repair of affected project boards additionally lasted until April 21, 05:04 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.

Update - The issue remains mitigated. Issues that were linked to projects during the incident may take approximately three more hours to render correctly while we complete a re-index.

Update - The degradation has been mitigated. We are monitoring to ensure stability.

Update - The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Update - The issue has been mitigated. Newly created issues linked to projects should now function as expected. Issues that were linked to projects during the incident may take approximately five hours to render correctly while we complete a re-index.

Update - A deployment to fix this issue of new issues not showing up in projects is underway.

Update - We continue to work on mitigation regarding new issues not showing on project boards.

Update - We continue to work on mitigation regarding new issues not showing on project boards.

Update - Code scanning default setup and Code Quality triggers are back up and running. PRs not processed before or during this incident will require a new push to trigger code scanning or code quality analysis.

Update - We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.

Update - We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.

Update - We are actively working to mitigate an issue affecting code scanning default setup and code quality features on pull requests. Users may experience pull request code scanning and code quality analyses not being triggered on new pull requests. Our engineering team has identified the root cause and working on mitigating the issue.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - On April 17, 2026, between 14:46 UTC and 15:12 UTC, users experienced a degraded web experience on GitHub.com. During this time, approximately 1.5% of web requests resulted in errors, with some users encountering slow page loads or failed requests. The issue was caused by capacity saturation of a caching component in one of our data center regions. We mitigated the issue by redirecting traffic to an unaffected region and rolling back a recent deployment. The incident was fully resolved at 15:18 UTC. We are taking steps to provide appropriate capacity for this caching path to prevent recurrence.

Monitoring - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Update - We have isolated a problematic component in our infrastructure and are working to mitigate. We will continue to post updates as we work toward resolution.

Update - We are experiencing an issue that impacts approximately 10% of traffic to the web, resulting in slow and failed calls. We are investigating and will continue to post updates as we work toward mitigation.

Update - Issues is experiencing degraded performance. We are continuing to investigate.

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - On April 16, 2026 between 09:30 UTC and 17:15 UTC, users experienced failures when attempting to connect to GitHub Codespaces via the VS Code editor. During this time, approximately 40% of codespace start operations failed. Users connecting via SSH were not impacted.

Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

Update - Our provider is implementing a mitigation and we are seeing signs of recovery.

Update - We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.

Update - Codespaces is experiencing degraded availability. We are continuing to investigate.

Update - We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.

Investigating - We are investigating reports of degraded performance for Codespaces

Resolved - On April 14, between 00:58 UTC and 06:08 UTC, GitHub Enterprise Cloud customers experienced 500 errors when attempting to access Copilot Insights pages which was caused by an authentication failure in our metrics pipeline. We fully mitigated the issue and validated the fix in production. Approximately 709 users were impacted. The total impact duration was approximately 5 hours and 10 minutes.

Update - This incident has been resolved. We will continue to monitor to ensure stability. Thank you for your patience and understanding as we addressed this issue.

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Update - We identified an issue that impacts the Copilot Dashboard on the Insights tab and are working on mitigation. We will continue to keep you updated on progress.

Update - The team continues to investigate issues accessing with Copilot Dashboard on the Insights tab.  We will continue providing updates on the progress towards mitigation.

Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.

Update - Degradation of Service - Insights Page

Investigating - We are investigating reports of impacted performance for some GitHub services.

Resolved - On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP 500 errors. This was due to an automated DNS management tool (octodns) erroneously deleting a DNS record for a Pages backend storage host after its upstream data source intermittently failed to return the record, causing the tool to treat it as stale and remove it.

Update - We have mitigated the issue with Pages.

Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

Update - We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.

Investigating - We are investigating reports of degraded availability for Pages

Resolved - On April 13, 2026, between 14:41 UTC and 17:29 UTC, the Copilot service experienced degraded performance. All Copilot users were impacted by increased latency, and approximately 20% experienced request failures when interacting with Copilot Cloud Agent (CCA). On average, request latency increased to approximately 950ms. The GitHub User Dashboard also displayed intermittent errors loading Copilot quota information. CCA and the User Dashboard were impacted for approximately 2 hours and 56 minutes.

Update - We have identified the root cause and are rolling out a fix for Copilot. The services should now be in recovery, with expected full recovery in 5 to 10 minutes.

Investigating - We are investigating reports of impacted performance for some GitHub services.