GitHub Status

May 12, 2026

No incidents reported today.

May 11, 2026

Incident with high errors on Git Operations

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.
May 11, 14:33 UTC

Investigating - We are investigating reports of degraded performance for Git Operations
May 11, 14:25 UTC

May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026

CCR and CCA failing to start for PR comments

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.
May 7, 06:56 UTC

Update - Copilot code review and cloud agents are starting again for pull requests, we are monitoring for full recovery.
May 7, 06:14 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
May 7, 06:13 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
May 7, 05:02 UTC

May 6, 2026

Incident with 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.
May 6, 19:04 UTC

Update - Mitigations have been fully applied and we are seeing full recovery of functionality on Pull Request threads. We are continuing to monitor to ensure sustained recovery.
May 6, 19:04 UTC

Update - Creation of new Pull Request threads (including line and file comments) continues to be affected although we are seeing partial recovery.

A mitigation is being applied to continue to accelerate recovery with complete recovery expected by 8:00pm UTC.

Top-level comments on pull requests still function and should remain usable during recovery. Opening and merging pull requests, actions, and other pull request operations remain functional.
May 6, 17:52 UTC

Update - Creation of new Pull Request threads (including line and file comments) continues to be affected.

Top-level comments on pull requests still function and should remain usable during recovery. Opening and merging pull requests, actions, and other pull request operations remain functional.

A mitigation is being applied. Recovery is expected to be gradual, with complete recovery expected by 8:00pm UTC.
May 6, 16:20 UTC

Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.
May 6, 16:07 UTC

Update - Creation of new Pull Request threads (including line and file comments) continues to be affected. We have identified the cause of the issue and have started taking steps to mitigate this issue.
May 6, 15:55 UTC

Update - We are investigating failures for new thread creation on Pull Requests. Responses to existing pull request threads are unaffected.
May 6, 15:28 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
May 6, 15:25 UTC

Disruption with some GitHub services

Resolved - On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by a configuration change to the service's network routing that inadvertently removed the ingress path for the service. The team reverted the change at 11:13 UTC which restored service. The incident remained open until 11:59 UTC while the team verified full recovery. We are taking steps to improve our deployment validation process to prevent similar configuration changes from impacting production traffic in the future.
May 6, 11:59 UTC

Update - We have applied a mitigation and Copilot services have recovered.
May 6, 11:59 UTC

Update - We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.
May 6, 11:25 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
May 6, 11:21 UTC

Incident with Actions, we are investigating reports of degraded availability

Resolved - On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed.

This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover.

We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.
May 6, 09:44 UTC

Update - Actions wait times have fully recovered.
May 6, 09:44 UTC

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
May 6, 09:19 UTC

Update - We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
May 6, 09:08 UTC

Update - Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue
May 6, 08:00 UTC

Investigating - We are investigating reports of degraded availability for Actions
May 6, 07:19 UTC

May 5, 2026

Increased Latency and Failures for SSH Git Operations

Resolved - Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones, were not affected.

The impact was caused by reduced SSH capacity at one of our data center sites. During a period of high traffic, the remaining hosts became overloaded, leading to connection exhaustion and some failures for SSH-based operations.

Additional capacity was provisioned to expand SSH capacity and resolve the incident. The expanded capacity was fully online by 18:18 UTC.

To reduce the likelihood of similar incidents, we will implement faster scaling solutions for SSH infrastructure and improved alerting for host availability and capacity thresholds.
May 5, 18:35 UTC

Update - We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.
May 5, 18:35 UTC

Monitoring - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
May 5, 18:25 UTC

Update - We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place.
May 5, 17:26 UTC

Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate.
May 5, 17:23 UTC

Monitoring - Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact.
May 5, 16:54 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
May 5, 16:49 UTC

Incident with Actions

Resolved - On May 5, 2026, from approximately 13:22 UTC to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded. 13.5% of jobs requesting a standard runner failed and ~16% of requested Larger Runners with private networking pinned to East US failed or were delayed by more than 5 minutes. Copilot Code Review requests were also impacted. Approximately 8,500 code review requests timed out during this window. Affected users saw an error comment on their pull requests and were able to retry by re-requesting a review. Most runner requests were picked up by other regions automatically, but a portion of requests still routing to East US were impacted.

This was triggered by a scale-up operation for hosted runner VMs in the East US region. This is a regular operation, but the VM create load hit an internal rate limit when VM creates pull images from storage. Existing backoff logic was not triggered because of the response code returned in this case. The rate limiting and VM creation failures were mitigated by reducing load to allow for recovery and allowing queued work to be processed. By 15:34 UTC, queued and failed job assignments were mostly mitigated, with less than 0.5% of runner assignments impacted between 15:34 and full recovery at 17:05.

We are improving our system’s throttling behavior when limits occur, improving our controls to more quickly mitigate similar situations in the future, and reviewing all limits end-to-end for similar operations. We also immediately paused all scale and similar operations until these changes are in place and validated.
May 5, 17:26 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
May 5, 17:11 UTC

Update - Standard hosted runners have now reached full recovery. Hosted Runners with Private Networking in the East US region remain degraded as we continue working with our compute provider to restore capacity. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
May 5, 17:11 UTC

Update - We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
May 5, 16:33 UTC

Update - We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
May 5, 15:54 UTC

Update - We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
May 5, 15:12 UTC

Update - We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different Azure region to mitigate the issue.
May 5, 14:14 UTC

Update - We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs
May 5, 13:48 UTC

Investigating - We are investigating reports of degraded availability for Actions
May 5, 13:37 UTC

May 4, 2026

Incident with Issues and Webhooks

Resolved - On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures to prevent recurrence.
May 4, 16:40 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
May 4, 16:36 UTC

Update - Webhooks is operating normally.
May 4, 16:35 UTC

Update - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
May 4, 16:35 UTC

Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
May 4, 16:34 UTC

Update - Pull Requests is operating normally.
May 4, 16:32 UTC

Update - Pages is operating normally.
May 4, 16:29 UTC

Update - Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.
May 4, 16:29 UTC

Update - Actions and Packages are operating normally.
May 4, 16:28 UTC

Update - Git Operations is operating normally.
May 4, 16:25 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
May 4, 16:06 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
May 4, 16:05 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
May 4, 15:56 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
May 4, 15:51 UTC

Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.
May 4, 15:51 UTC

Update - Packages is experiencing degraded performance. We are continuing to investigate.
May 4, 15:50 UTC

Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
May 4, 15:48 UTC

Update - We are investigating Increased latency and timeouts across multiple GitHub services.
May 4, 15:48 UTC

Investigating - We are investigating reports of degraded performance for Issues and Webhooks
May 4, 15:45 UTC

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

Incomplete pull request results in repositories

Resolved - On April 28, 2026, at approximately 14:07 UTC, GitHub received reports that pull requests were missing from search results across global and repository /pulls pages.

The issue was caused by a manually invoked repair job intended for a single repository, which was executed without the required safety flags. During execution of the repair job, the database query remained correctly scoped to the repo’s PR IDs. However, the Elasticsearch reconciliation logic did not apply the same scope. It interpreted the min and max PR IDs as a continuous range, causing unrelated PR documents across other repos to be marked for deletion. This resulted in the removal of 1,789,756,838 PR documents from the search index, approximately 49% of indexed PR documents.

Customer impact was limited to PR search and list discoverability. Primary storage was unaffected, and there was no impact to opening, updating, or merging PRs.

The issue was identified ~10 minutes after initial customer reports. Because it affected search index completeness rather than service availability, it was not caught by existing monitoring.

The root cause was a flaw in the search document repair framework: it allowed a scoped reconciliation to run without enforcing a matching Elasticsearch query scope. This created a destructive mismatch between the source-of-truth and the index. The issue was compounded by the ability to trigger the job from the production console without safety defaults. Prior testing focused only on safe backfill scenarios and did not cover this reconciliation path. Additionally, there was no automated detection for large-volume deletions in Elasticsearch.

We mitigated the incident through three parallel actions: (1) Deployed a MySQL-backed search fallback for the most active repos by traffic to restore PR visibility for highly impacted users (2) Initiated a snapshot restore and reindex process to repopulate missing pull request documents in Elasticsearch (3) Added a degradation notice on PR pages to inform users of incomplete search results while recovery was in progress. The incident was resolved on May 1, 2026 at 4:15 UTC, following completion and validation of the reindex process.

To prevent recurrence, we are prioritizing improvements to the repair framework and safeguards. These include enforcing scoped query alignment between primary storage and Elasticsearch, preventing destructive operations without explicit opt-in, strengthening guardrails for manual repair jobs, and evaluating restrictions on production console access.

In parallel, we are expanding automated test coverage for reconciliation safety invariants and introducing detection for anomalous deletion patterns in Elasticsearch so similar issues can be identified or blocked earlier.

We are committed to improving the safety and reliability of our repair systems and ensuring that operational workflows are resilient to both software defects and manual invocation risks.
May 1, 04:15 UTC

Update - 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.
May 1, 04:11 UTC

Update - 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.
Apr 30, 03:49 UTC

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

Update - Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.
Apr 29, 00:40 UTC

Update - We have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress.
Apr 28, 22:46 UTC

Update - 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.
Apr 28, 21:43 UTC

Update - 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.
Apr 28, 15:58 UTC

Update - 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.
Apr 28, 14:51 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 28, 14:17 UTC

Apr 30, 2026

Apr 29, 2026

Apr 28, 2026

Disruption with some GitHub services

Resolved - On April 28, 2026, from approximately 12:41 UTC to 17:09 UTC, GitHub Actions jobs using Standard Ubuntu 22 and Ubuntu 24 hosted runners experienced run start delays. Approximately 8% of hosted runner jobs using Ubuntu 22 and Ubuntu 24 experienced delays greater than 5 minutes or failures. Larger and self-hosted runners were not impacted.

This was caused by a performance regression introduced in the VM reimage process. That reimage delay lowered the overall capacity of runners available to pick up new jobs. This was mitigated with a rollback to a known good image version.

We are addressing the core issue with reimage performance and improving the granularity of reimage telemetry across our services and our compute provider to more quickly diagnose similar issues in the future. Finally, we are evaluating other rollout changes to automatically detect similar regressions.
Apr 28, 17:09 UTC

Monitoring - Actions is operating normally.
Apr 28, 17:08 UTC

Update - Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.
Apr 28, 16:36 UTC

Update - 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.
Apr 28, 15:41 UTC

Update - We've applied a mitigation to unblock running Actions. We're continuing to monitor.
Apr 28, 15:20 UTC

Update - 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.
Apr 28, 14:49 UTC

Investigating - Actions is experiencing degraded performance. We are continuing to investigate.
Apr 28, 14:02 UTC

Monitoring - Actions is experiencing capacity constraints with hosted ubuntu-latest and ubuntu-24.02, leading to high wait times. Other hosted labels and self-hosted runners are not impacted.
Apr 28, 13:59 UTC

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

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents