GitHub Status

Apr 25, 2026

Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region

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.
Apr 25, 00:36 UTC

Update - This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/
Apr 24, 19:14 UTC

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.
Apr 24, 19:09 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 24, 19:02 UTC

Apr 24, 2026

Apr 23, 2026

Incident with Pull Requests

Resolved - This incident has been resolved and we've contacted repository administrators via email who have impacted branches.

Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.
Apr 23, 21:43 UTC

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.

This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
Apr 23, 21:18 UTC

Update - Pull Requests is operating normally.
Apr 23, 20:47 UTC

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.
Apr 23, 19:58 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 23, 19:50 UTC

Disruption with users unable to start Claude and Codex agent task from the web

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.
Apr 23, 19:42 UTC

Update - We have identified the root cause of the issue and are working on mitigation.
Apr 23, 19:33 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 23, 19:28 UTC

Incident with multiple 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.
Apr 23, 17:30 UTC

Update - Webhooks is operating normally.
Apr 23, 17:10 UTC

Update - Many services are mitigated and are validating the remaining services.
Apr 23, 17:04 UTC

Update - The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.
Apr 23, 17:03 UTC

Update - We have identified the root problem and are working on mitigation.
Apr 23, 16:52 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Apr 23, 16:34 UTC

Update - We are investigating multiple unavailable services.
Apr 23, 16:19 UTC

Investigating - We are investigating reports of degraded availability for Copilot and Webhooks
Apr 23, 16:12 UTC

Investigating errors on GitHub

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.
Apr 23, 15:18 UTC

Monitoring - The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.
Apr 23, 15:02 UTC

Update - A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.
Apr 23, 15:02 UTC

Update - Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.
Apr 23, 14:51 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:44 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:42 UTC

Update - Packages is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:41 UTC

Investigating - We are investigating reports of degraded performance for Actions
Apr 23, 14:40 UTC

Apr 22, 2026

Disruption with 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.
Apr 22, 22:43 UTC

Update - We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.
Apr 22, 22:09 UTC

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.

Apr 22, 20:37 UTC

Update - Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.
Apr 22, 20:02 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Apr 22, 19:55 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 22, 19:53 UTC

Disruption with Copilot chat and Copilot Coding Agent

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.
Apr 22, 19:18 UTC

Update - Copilot cloud agent and chat are mitigated for github.com.
Apr 22, 18:05 UTC

Update - We are now seeing recovery for Copilot cloud agent.
Apr 22, 17:49 UTC

Update - Mitigation is progressing for Copilot chat and cloud agent recovery.
Apr 22, 17:40 UTC

Update - Mitigation is progressing for Copilot chat and cloud agent.
Apr 22, 16:58 UTC

Update - We continue to work on mitigation for Copilot chat and cloud agent.
Apr 22, 16:24 UTC

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.
Apr 22, 15:43 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 22, 15:35 UTC

Disruption with projects service

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.
Apr 22, 01:24 UTC

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.
Apr 22, 00:00 UTC

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.
Apr 21, 22:49 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 21, 21:15 UTC

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.
Apr 21, 19:41 UTC

Update - The queues are continuing to decrease and we are working to accelerate the rate of processing through the queues.
Apr 21, 17:21 UTC

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.
Apr 21, 16:45 UTC

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.
Apr 21, 16:18 UTC

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.
Apr 21, 15:42 UTC

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.
Apr 21, 15:07 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 21, 15:03 UTC

Apr 21, 2026

Partial degradation for code scanning default setup and for code quality

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

During this time, code scanning default setup and code quality analyses were not triggered on newly opened pull requests. Additionally, newly created issues were not appearing on project boards.

The cause was a serialization error that prevented proper triggering of code scanning, code quality analyses, and project board updates.

We mitigated the issue by deploying a fix, restoring event publishing for code scanning and code quality. For project boards, an additional code change was deployed to update event consumers, followed by a reindex of affected project items.

We are working to prevent recurrence by strengthening our schema validations and improving monitoring for drops in publishing on critical hydro topics.
Apr 21, 05:04 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 21, 04:18 UTC

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.
Apr 21, 03:10 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 20, 21:36 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 20, 18:21 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 20, 18:20 UTC

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.
Apr 20, 18:20 UTC

Update - A deployment to fix this issue of new issues not showing up in projects is underway.
Apr 20, 18:08 UTC

Update - We continue to work on mitigation regarding new issues not showing on project boards.
Apr 20, 17:32 UTC

Update - We continue to work on mitigation regarding new issues not showing on project boards.
Apr 20, 16:48 UTC

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.

We are seeing problems with new issues not showing on project boards and are working on mitigation.
Apr 20, 16:16 UTC

Update - We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.
Apr 20, 15:20 UTC

Update - We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.
Apr 20, 14:38 UTC

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.
Apr 20, 13:57 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 20, 13:28 UTC

Apr 20, 2026

Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026

Disruption with 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.
Apr 17, 15:18 UTC

Monitoring - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Apr 17, 15:18 UTC

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.
Apr 17, 15:08 UTC

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.
Apr 17, 14:57 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Apr 17, 14:56 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 17, 14:56 UTC

Apr 16, 2026

Incident with Codespaces

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.

The issue was caused by a failure in an upstream download service that prevented the VS Code Server from being retrieved during codespace startup. The impact was mitigated by implementing a workaround to use an alternative download path when the primary endpoint is degraded.

We are working with the upstream dependency to address the root cause of the download service failure, and we are improving our fallback mechanisms to reduce the impact of similar upstream failures in the future.
Apr 16, 18:28 UTC

Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
Apr 16, 18:22 UTC

Update - Our provider is implementing a mitigation and we are seeing signs of recovery.
Apr 16, 16:37 UTC

Update - We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.
Apr 16, 15:49 UTC

Update - Codespaces is experiencing degraded availability. We are continuing to investigate.
Apr 16, 15:41 UTC

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.
Apr 16, 15:08 UTC

Investigating - We are investigating reports of degraded performance for Codespaces
Apr 16, 15:06 UTC

Apr 15, 2026

No incidents reported.

Apr 14, 2026

Disruption with some GitHub services

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.

Our investigation determined the incident was caused by a change in a tenant credential which caused authentication errors to retrieve the required data needed on our Copilot Insights pages.

We understand this disruption impacted customers' ability to access the Copilot Insights page. To prevent similar issues and reduce resolution time in the future, we are investing in improved diagnostics tooling to quickly identify the root cause of failures, enhanced monitoring, and alerting to detect issues at a more granular level.

GitHub is a critical infrastructure for your work, your teams, and your businesses. We are focused on these remediations and continued reliability improvements for Copilot Insights and related metrics experiences.
Apr 14, 06:08 UTC

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.
Apr 14, 06:07 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 14, 06:07 UTC

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.
Apr 14, 04:40 UTC

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.
Apr 14, 03:47 UTC

Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.
Apr 14, 02:40 UTC

Update - Degradation of Service - Insights Page
Apr 14, 02:37 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 14, 01:57 UTC

Apr 13, 2026

Incident with Pages

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.

We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.
Apr 13, 20:35 UTC

Update - We have mitigated the issue with Pages.
Apr 13, 20:32 UTC

Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Apr 13, 20:30 UTC

Update - We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.
Apr 13, 19:57 UTC

Investigating - We are investigating reports of degraded availability for Pages
Apr 13, 19:56 UTC

Disruption with some GitHub services

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.

This was due to an infrastructure change that reduced the available compute capacity for a backend service responsible for Copilot rate limiting and quota management. The reduced capacity caused resource exhaustion under normal traffic load, leading to cascading failures in downstream request processing.

We mitigated the incident by increasing compute resources allocated to the affected service and scaling out the number of service instances to distribute load more effectively.

We are working to improve proactive capacity monitoring to detect resource degradation before it impacts users, reviewing retry and timeout configurations across dependent services to reduce amplification during degraded states, and evaluating connection management strategies to improve resilience under constrained resources.
Apr 13, 17:40 UTC

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.
Apr 13, 16:59 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 13, 16:41 UTC

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents