GitHub Outage History

We are investigating reports of degraded performance for Pull Requests

After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents. No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again.

We are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact. We are taking a measured approach to safely backfill data and will share additional updates as progress continues.

Elastic search reindexing of pull requests is continuing. All data is preserved, but may not be available on pages relying on elasticsearch until the reindex is complete. Pages and APIs that do not rely on elasticsearch, including the GitHub CLI (gh pr list) and API (/repos/{owner}/{repo}/pulls), are not impacted and can be used to retrieve pull request data in the interim.

We have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress.

Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.

We have restored search/indexing functionality for over 99% of impacted pull requests. We are continuing to address the remaining affected pull requests and are reviewing outstanding gaps as part of the restoration process.

We have repaired the missing search records for affected Pull Requests and are working to identify and repair records left in a stale state after the recovery.

This incident has been resolved. Search and indexing functionality for pull requests are now fully restored. 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.

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

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

We're still investigating the root cause for run start delays and failures for Actions hosted Ubuntu jobs, around 5% of jobs are impacted as of now.

We've applied a mitigation to unblock running Actions. We're continuing to monitor.

Currently less than 2% of hosted ubuntu-latest and ubuntu-24.04 runs are delayed or failing. We are continuing to monitor for full recovery.

Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.

We are investigating reports of degraded performance for Actions

Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.

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

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

Pull Requests is experiencing degraded performance. We are continuing to investigate.

Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.

We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause

Pull Requests is experiencing degraded availability. We are continuing to investigate.

We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery

Pull Requests is experiencing degraded performance. We are continuing to investigate.

We've applied a mitigation and continuing to monitor

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

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.

This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/

We are investigating reports of degraded performance for Pull Requests

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.

Pull Requests is operating normally.

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.

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

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

We are investigating reports of degraded availability for Copilot and Webhooks

We are investigating multiple unavailable services.

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

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

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

Many services are mitigated and are validating the remaining services.

Webhooks is operating normally.

We are investigating reports of degraded performance for Actions

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

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

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

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

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

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

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.

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

Mitigation is progressing for Copilot chat and cloud agent.

Mitigation is progressing for Copilot chat and cloud agent recovery.

We are now seeing recovery for Copilot cloud agent.

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

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

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.

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.

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.

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.

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

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.

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

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.

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

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

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.

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

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

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

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.

We are investigating reports of degraded performance for Codespaces

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.

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

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

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

We are investigating reports of degraded availability for Pages

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

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

We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.

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

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

When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running. We are investigating.

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

A routine credential rotation has failed for our our audit logs service; we have re-deployed our service and are waiting for recovery.

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

We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.

We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data. We will update again within 2 hours.

We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.

We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.

Code search has recovered and is serving production traffic.

We are investigating reports of degraded performance for Copilot

We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.

Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.

We are investigating reports of degraded performance for Pull Requests

We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.

We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.

We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.

We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.

Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.

We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.

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

We're seeing issues related to metered billing reports, intermittently affecting metered usage graphs and reports on the billing page. We have identified an issue with a data store, and are working on mitigations.

We're continuing to see high failure rates on billing report generation, and are working on mitigations for a data store related to billing reports.

We are seeing a high number of 500s due to timeouts across GitHub services. We are redeploying some of our core services and we expect that this allow us to recover.

We have applied mitigations to a data store related to billing reports, and are seeing partial recovery to billing report generation. We continue to monitor for full recovery.

We are investigating reports of degraded performance for Actions and Pull Requests

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

We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.

We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.

We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.

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

We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.

We are rolling out our mitigation and are seeing recovery.

We are investigating reports of degraded performance for Git Operations

We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations

We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate

We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations

We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete.

We have completed the rollout of our new network path and are monitoring its impact.

We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast.

We have reached stability with git operations through our changes deployed today.