May <var data-var='date'>12</var>, <var data-var='time'>17:43</var> UTC 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 <var data-var='date'>12</var>, <var data-var='time'>17:43</var> UTC Update - All services have fully recovered.May <var data-var='date'>12</var>, <var data-var='time'>16:59</var> UTC Update - CodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.May <var data-var='date'>12</var>, <var data-var='time'>16:29</var> UTC Update - Webhooks have fully recovered. Continuing to work on recovery for the other services.May <var data-var='date'>12</var>, <var data-var='time'>16:28</var> UTC Update - Webhooks is operating normally.May <var data-var='date'>12</var>, <var data-var='time'>16:18</var> UTC Update - We've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.May <var data-var='date'>12</var>, <var data-var='time'>15:44</var> UTC Update - Webhooks is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'>12</var>, <var data-var='time'>15:42</var> UTC Update - We're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.May <var data-var='date'>12</var>, <var data-var='time'>15:13</var> UTC Update - CodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.May <var data-var='date'>12</var>, <var data-var='time'>14:38</var> UTC Investigating - We are investigating reports of degraded performance for CodeQL

Incident with CodeQL, Webhooks, Notifications, and Slack Integration

May <var data-var='date'>11</var>, <var data-var='time'>14:33</var> UTC 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 <var data-var='date'>11</var>, <var data-var='time'>14:25</var> UTC Investigating - We are investigating reports of degraded performance for Git Operations

Incident with high errors on Git Operations

May <var data-var='date'> 7</var>, <var data-var='time'>06:56</var> UTC 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 <var data-var='date'> 7</var>, <var data-var='time'>06:14</var> UTC Update - Copilot code review and cloud agents are starting again for pull requests, we are monitoring for full recovery.May <var data-var='date'> 7</var>, <var data-var='time'>06:13</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 7</var>, <var data-var='time'>05:02</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

CCR and CCA failing to start for PR comments

May <var data-var='date'> 6</var>, <var data-var='time'>19:04</var> UTC Resolved - On May 6, 2026 between 15:12 and 19:02 UTC creation of new pull request review threads on GitHub.com failed. This included new line comments and file comments on pull requests. Existing PRs and previously created comments were unaffected. This incident was caused by a 32-bit integer key reaching its maximum value in a Vitess lookup table used during PR thread creation. The primary table had been migrated to a 64-bit integer key but the Vitesse lookup table remained 32-bit. Once the values in the primary table passed the available 32-bit ID space in the lookup table, attempts to create new review threads began failing, resulting in near 100% failure rate for new thread creation requests. We mitigated the issue by updating the impacted lookup table definitions across all shards to use 64-bit integer column types, increasing the available ID range and restoring normal operation. Service was fully restored once the schema changes competed globally. To help prevent similar incidents, we are expanding existing monitoring of database columns to include Vitess lookup tables to notify in advance of any tables that is approaching a column size limit. This work is intended to provide earlier detection of columns approaching size limits before customer impact occurs.May <var data-var='date'> 6</var>, <var data-var='time'>19:04</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>17:52</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>16:20</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>16:07</var> UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.May <var data-var='date'> 6</var>, <var data-var='time'>15:55</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>15:28</var> UTC Update - We are investigating failures for new thread creation on Pull Requests. Responses to existing pull request threads are unaffected.May <var data-var='date'> 6</var>, <var data-var='time'>15:25</var> UTC Investigating - We are investigating reports of degraded performance for Pull Requests

Incident with Pull Requests

May <var data-var='date'> 6</var>, <var data-var='time'>11:59</var> UTC 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 <var data-var='date'> 6</var>, <var data-var='time'>11:59</var> UTC Update - We have applied a mitigation and Copilot services have recovered.May <var data-var='date'> 6</var>, <var data-var='time'>11:25</var> UTC Update - We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.May <var data-var='date'> 6</var>, <var data-var='time'>11:21</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with some GitHub services

May <var data-var='date'> 6</var>, <var data-var='time'>09:44</var> UTC 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 <var data-var='date'> 6</var>, <var data-var='time'>09:44</var> UTC Update - Actions wait times have fully recovered.May <var data-var='date'> 6</var>, <var data-var='time'>09:19</var> UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 6</var>, <var data-var='time'>09:08</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>08:00</var> UTC Update - Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issueMay <var data-var='date'> 6</var>, <var data-var='time'>07:19</var> UTC Investigating - We are investigating reports of degraded availability for Actions

Incident with Actions, we are investigating reports of degraded availability

May <var data-var='date'> 5</var>, <var data-var='time'>18:35</var> UTC 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 <var data-var='date'> 5</var>, <var data-var='time'>18:35</var> UTC Update - We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.May <var data-var='date'> 5</var>, <var data-var='time'>18:25</var> UTC Monitoring - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 5</var>, <var data-var='time'>17:26</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>17:23</var> UTC Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 5</var>, <var data-var='time'>16:54</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>16:49</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Increased Latency and Failures for SSH Git Operations

May <var data-var='date'> 5</var>, <var data-var='time'>17:26</var> UTC 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 <var data-var='date'> 5</var>, <var data-var='time'>17:11</var> UTC Update - Actions is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 5</var>, <var data-var='time'>17:11</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>16:33</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>15:54</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>15:12</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>14:14</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>13:48</var> UTC Update - We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runsMay <var data-var='date'> 5</var>, <var data-var='time'>13:37</var> UTC Investigating - We are investigating reports of degraded availability for Actions

Incident with Actions

May <var data-var='date'> 4</var>, <var data-var='time'>16:40</var> UTC 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 <var data-var='date'> 4</var>, <var data-var='time'>16:36</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 4</var>, <var data-var='time'>16:35</var> UTC Update - Webhooks is operating normally.May <var data-var='date'> 4</var>, <var data-var='time'>16:35</var> UTC Update - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 4</var>, <var data-var='time'>16:34</var> UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.May <var data-var='date'> 4</var>, <var data-var='time'>16:32</var> UTC Update - Pull Requests is operating normally.May <var data-var='date'> 4</var>, <var data-var='time'>16:29</var> UTC Update - Pages is operating normally.May <var data-var='date'> 4</var>, <var data-var='time'>16:29</var> UTC Update - Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.May <var data-var='date'> 4</var>, <var data-var='time'>16:28</var> UTC Update - Actions and Packages are operating normally.May <var data-var='date'> 4</var>, <var data-var='time'>16:25</var> UTC Update - Git Operations is operating normally.May <var data-var='date'> 4</var>, <var data-var='time'>16:06</var> UTC Update - Pages is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>16:05</var> UTC Update - Codespaces is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:56</var> UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:51</var> UTC Update - Actions is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:51</var> UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:50</var> UTC Update - Packages is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:48</var> UTC Update - Git Operations is experiencing degraded performance. We are continuing to investigate.May <var data-var='date'> 4</var>, <var data-var='time'>15:48</var> UTC Update - We are investigating Increased latency and timeouts across multiple GitHub services.May <var data-var='date'> 4</var>, <var data-var='time'>15:45</var> UTC Investigating - We are investigating reports of degraded performance for Issues and Webhooks

Incident with Issues and Webhooks

May <var data-var='date'> 1</var>, <var data-var='time'>04:15</var> UTC 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 <var data-var='date'> 1</var>, <var data-var='time'>04:11</var> 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.Apr <var data-var='date'>30</var>, <var data-var='time'>03:49</var> 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 <var data-var='date'>29</var>, <var data-var='time'>22:22</var> 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 <var data-var='date'>29</var>, <var data-var='time'>00:40</var> UTC Update - Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.Apr <var data-var='date'>28</var>, <var data-var='time'>22:46</var> 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 <var data-var='date'>28</var>, <var data-var='time'>21:43</var> 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 <var data-var='date'>28</var>, <var data-var='time'>15:58</var> 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 <var data-var='date'>28</var>, <var data-var='time'>14:51</var> 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 <var data-var='date'>28</var>, <var data-var='time'>14:17</var> UTC Investigating - We are investigating reports of degraded performance for Pull Requests

Incomplete pull request results in repositories

Apr <var data-var='date'>28</var>, <var data-var='time'>17:09</var> UTC 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 <var data-var='date'>28</var>, <var data-var='time'>17:08</var> UTC Monitoring - Actions is operating normally.Apr <var data-var='date'>28</var>, <var data-var='time'>16:36</var> UTC Update - Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.Apr <var data-var='date'>28</var>, <var data-var='time'>15:41</var> 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 <var data-var='date'>28</var>, <var data-var='time'>15:20</var> UTC Update - We've applied a mitigation to unblock running Actions. We're continuing to monitor.Apr <var data-var='date'>28</var>, <var data-var='time'>14:49</var> 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 <var data-var='date'>28</var>, <var data-var='time'>14:02</var> UTC Investigating - Actions is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>28</var>, <var data-var='time'>13:59</var> 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 <var data-var='date'>28</var>, <var data-var='time'>13:59</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Apr <var data-var='date'>27</var>, <var data-var='time'>22:46</var> UTC Resolved - On April 27, 2026 between 16:15 UTC and 22:46 UTC, GitHub search services experienced degraded connectivity due to saturation of the load balancing tier deployed in front of our search infrastructure. This resulted in intermittent failures for services relying on our search data including Issues, Pull Requests, Projects, Repositories, Actions, Package Registry and Dependabot Alerts. The impact was varied by search target, with services seeing up to 65% of searches timing out or returning an error between 16:15 UTC and 18:00 UTC. We detected the drop in search results through our ongoing monitoring and declared an incident at 16:21 UTC when we determined the issues would not self-heal. We tracked the incident as mitigated as of 21:33 UTC and monitored the systems until 22:46 UTC when we declared the incident resolved. Our existing monitoring did not classify the increased scraping as a risk and this dimension of the incident was only discovered while working to mitigate. The saturation was caused by a large influx of anonymous distributed scraping traffic that was crafted to avoid our public API rate limits. This scraping traffic made up 30% of the day’s total search traffic, but it was concentrated within a four-hour period. The traffic originated from over 600,000 Unique IP addresses, with matching actor information across the board. To mitigate, we immediately focused on relieving pressure from the load balancers while simultaneously working on scaling the load balancing tier, blocking the anomalous traffic and applying tuning to the balancers to fully resolve the incident. Looking ahead, we’ve not only scaled the load balancer tier, but applied optimizations to improve our connection handling and re-use to reduce the possibility that a saturation event like this can re-occur. We’ve also added new monitors and controls within the platform to allow us to restrict anonymous traffic to mitigate the impact to our registered users. Apr <var data-var='date'>27</var>, <var data-var='time'>22:44</var> UTC Update - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>27</var>, <var data-var='time'>22:35</var> UTC Update - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>27</var>, <var data-var='time'>21:33</var> UTC Monitoring - The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>27</var>, <var data-var='time'>21:32</var> UTC Update - We've applied a mitigation and continuing to monitorApr <var data-var='date'>27</var>, <var data-var='time'>20:06</var> UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>27</var>, <var data-var='time'>19:50</var> UTC Update - 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 recoveryApr <var data-var='date'>27</var>, <var data-var='time'>18:19</var> UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.Apr <var data-var='date'>27</var>, <var data-var='time'>18:17</var> UTC Update - We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root causeApr <var data-var='date'>27</var>, <var data-var='time'>17:35</var> UTC Update - 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.Apr <var data-var='date'>27</var>, <var data-var='time'>16:53</var> UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>27</var>, <var data-var='time'>16:39</var> UTC Update - Packages is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>27</var>, <var data-var='time'>16:36</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>27</var>, <var data-var='time'>16:33</var> UTC Update - 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.Apr <var data-var='date'>27</var>, <var data-var='time'>16:31</var> UTC Investigating - We are investigating reports of degraded performance for Actions

GitHub search is degraded

Apr <var data-var='date'>27</var>, <var data-var='time'>19:02</var> UTC Resolved - On April 22, 2026 from 18:49 to 19:32 UTC , the Copilot Cloud Agent service began failing during session execution for users running the Agent HQ Codex agent. Codex agent sessions failed to start for all entry points (issue assignment, @copilot comment mentions). 0.5% of total Copilot Cloud Agent jobs were impacted (~2,000 failed jobs). Copilot and other agent sessions were unaffected. This was caused by a model resolution mismatch in Codex agent sessions, resulting in an incompatible model being used at runtime. A mitigation was deployed to select a stable default model for Codex agent sessions. We are working to harden the underlying model-resolution path so it correctly scopes to the requesting agent's supported models to prevent similar failure mode in the future.Apr <var data-var='date'>27</var>, <var data-var='time'>19:01</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>27</var>, <var data-var='time'>17:26</var> UTC Update - We've found the issue and are working on deploying a solution to get Codex agent runs working again.Apr <var data-var='date'>27</var>, <var data-var='time'>17:01</var> UTC 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 remediationApr <var data-var='date'>27</var>, <var data-var='time'>16:48</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Apr <var data-var='date'>25</var>, <var data-var='time'>00:36</var> UTC Resolved - On April 24, 2026, from approximately 11:39 UTC to April 25, 2026 at 00:15 UTC, GitHub Actions experienced delays and timeouts for Larger Hosted Runner jobs using VNet injection in the East US region without a failover region configured. Standard and Self-hosted runners were not impacted. This was caused by backend failures in our compute provider’s provisioning, scaling, and update operations for VMs in the East US region and mitigated by a rollback across all affected Availability Zones. More detail is available at https://azure.status.microsoft/en-us/status/history/?trackingId=5GP8-W0G. We are working to improve the reliability of our annotations for jobs impacted by regional issues and are adding system log notifications as an additional customer communication channel alongside annotations. VNet Failover is also now in public preview, allowing customers to evacuate Larger Hosted Runners using VNet injection in cases like this.Apr <var data-var='date'>24</var>, <var data-var='time'>19:14</var> UTC Update - This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/Apr <var data-var='date'>24</var>, <var data-var='time'>19:09</var> 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 <var data-var='date'>24</var>, <var data-var='time'>19:02</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

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

Apr <var data-var='date'>23</var>, <var data-var='time'>21:43</var> UTC 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. During the impact window 2,092 pull requests were affected. The issue did not affect pull requests merged outside of merge queue, nor merge queue groups using the merge or rebase methods. It took approximately 3 hours and 33 minutes to identify the issue. The change completed deployment at approximately 16:05 UTC, and we became aware at 19:38 UTC following an increase in customer support inquiries. Because the issue affected merge commit correctness rather than availability, it was not detected by existing automated monitoring and was identified through customer reports. The regression was introduced by a new code path that adjusted merge base computation for merge queue ref updates. This code path was intended to be gated behind a feature flag for an unreleased feature, but the gating was incomplete. As a result, the new behavior was inadvertently applied to squash merge groups, producing an incorrect three-way merge. This caused subsequent squash merges to revert changes from earlier pull requests and, in some cases, changes between their starting points. We mitigated the incident by reverting the code change and force-deploying the fix across all environments. After resolution, we identified affected repositories and sent targeted remediation instructions to repository administrators with step-by-step recovery guidance. The regression was not identified during internal validation. Existing test coverage primarily exercised single-PR merge queue groups, which did not exhibit the faulty base-reference calculation. Because automated checks did not validate merge correctness for multi-PR squash groups, the defect surfaced only in production. To prevent recurrence, GitHub is expanding test coverage for merge correctness validation. We are broadening automated coverage for merge queue operations, including regression checks that validate resulting Git contents across supported configurations, so issues affecting merge correctness are caught before reaching production. We are committed to ensuring the correctness and reliability of merge queue operations. These actions will reduce the risk of similar regressions and improve confidence in future changes to the Pull Requests service.Apr <var data-var='date'>23</var>, <var data-var='time'>21:18</var> 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 <var data-var='date'>23</var>, <var data-var='time'>20:47</var> UTC Update - Pull Requests is operating normally.Apr <var data-var='date'>23</var>, <var data-var='time'>19:58</var> 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 <var data-var='date'>23</var>, <var data-var='time'>19:50</var> UTC Investigating - We are investigating reports of degraded performance for Pull Requests

Apr <var data-var='date'>23</var>, <var data-var='time'>19:42</var> UTC Resolved - Between 18:45 and 19:42 UTC on April 23, users were unable to start new agent tasks using either Claude or Codex agent on github.com. This was caused by a code change to how Copilot mission control routes task creation requests. Ongoing agent tasks and other Copilot agent features were not affected. We mitigated the impact by reverting the breaking change. We are adding extra monitoring and integration test coverage for the task creation path to prevent future recurrence.Apr <var data-var='date'>23</var>, <var data-var='time'>19:33</var> UTC Update - We have identified the root cause of the issue and are working on mitigation.Apr <var data-var='date'>23</var>, <var data-var='time'>19:28</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

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

Apr <var data-var='date'>23</var>, <var data-var='time'>17:30</var> UTC Resolved - On April 23, 2026, between 16:03 UTC and 17:27 UTC, multiple GitHub services experienced elevated error rates and degraded performance due to DNS resolution failures originating from our DNS infrastructure in our VA3 datacenter. Approximately 5–7% of overall traffic was affected during the impact window: - Webhooks: ~0.35% of API requests returned 5xx (peak ~0.39%). ~0.88% of requests exceeded 3s latency; at peak, >3s responses represented ~10% of Webhooks API traffic. - Copilot Metrics: ~9% of Copilot Insights dashboard requests returned 5xx. - Copilot cloud agents: ~10% of cloud agent sessions were affected and failing. - Octoshift: 0.88% of active repo migrations failed and 79% saw elevated durations (avg. 5.2 min) during this period. - Git Operations: averaged 1.25% errors over the duration of the incident, with a peak of 2.07% errors. - Actions: Workflow run status updates experienced delays of up to ~8s over the duration of the incident window. Our DNS infrastructure in VA3 entered a degraded state and began intermittently returning NXDOMAIN responses and timing out on lookups for both internal service discovery and external endpoints. This caused a cascading impact across the dependent services listed above. We identified a specific load pattern under which our DNS resolvers began failing. The evidence points to a recently introduced traffic-balancing mechanism, rolled out progressively to support our growth, as the root cause. We have since reverted this change. We are immediately prioritizing investments in a more controlled rollout and validation process, including a dedicated environment to safely shadow production DNS traffic and detect these failure modes before they can affect production.Apr <var data-var='date'>23</var>, <var data-var='time'>17:10</var> UTC Update - Webhooks is operating normally.Apr <var data-var='date'>23</var>, <var data-var='time'>17:04</var> UTC Update - Many services are mitigated and are validating the remaining services.Apr <var data-var='date'>23</var>, <var data-var='time'>17:03</var> UTC Update - The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>23</var>, <var data-var='time'>16:52</var> UTC Update - We have identified the root problem and are working on mitigation.Apr <var data-var='date'>23</var>, <var data-var='time'>16:34</var> UTC Update - Actions is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>23</var>, <var data-var='time'>16:19</var> UTC Update - We are investigating multiple unavailable services.Apr <var data-var='date'>23</var>, <var data-var='time'>16:12</var> UTC Investigating - We are investigating reports of degraded availability for Copilot and Webhooks

Incident with multiple GitHub services

Apr <var data-var='date'>23</var>, <var data-var='time'>15:18</var> UTC Resolved - On April 23, 2026 between 14:30 UTC and 15:18 UTC multiple services were degraded on github.com. During this time approximately 1.5% of all web requests resulted in a 5xx status and unicorn pages for github.com users. We also saw elevated error rates across Actions workflow runs, Copilot, Codespaces and Packages, leading to degraded experiences during this timeframe. Codespaces impact peaked at 45% failures for create requests and 65% failures for resume requests. Packages impact was mainly Maven related with 50% failure rates in downloads and 70% failure rates in uploads. Actions experienced a peak of 8% of failed jobs and up to 85% of jobs impacted by run start delays of more than 5 minutes. This was due to a configuration change to an internal billing service that led to a cache being overwhelmed and causing requests to time out. These timeouts cascaded across multiple services and eventually caused requests to queue up and exhaust web request workers. This configuration change was reverted at 14:42 UTC and following this, all services began to see recovery immediately. To prevent this situation in the future, we are taking steps to ensure that failures and timeouts in the billing service don’t cascade to other services causing impact. This includes implementing more aggressive timeouts on callers of these billing services, adding circuit breaker configurations for cache timeouts and using more resilient cache options. We have also decreased max request timeouts within the billing service that caused impact and added more capacity to our cache to prevent traffic spikes from having the same impact.Apr <var data-var='date'>23</var>, <var data-var='time'>15:02</var> UTC Monitoring - The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>23</var>, <var data-var='time'>15:02</var> UTC Update - A mitigation was applied and services have recovered.  Actions is working through queued work before fully recovering.Apr <var data-var='date'>23</var>, <var data-var='time'>14:51</var> UTC Update - Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.Apr <var data-var='date'>23</var>, <var data-var='time'>14:44</var> UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>23</var>, <var data-var='time'>14:42</var> UTC Update - Codespaces is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>23</var>, <var data-var='time'>14:41</var> UTC Update - Packages is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>23</var>, <var data-var='time'>14:40</var> UTC Investigating - We are investigating reports of degraded performance for Actions

Investigating errors on GitHub

Apr <var data-var='date'>22</var>, <var data-var='time'>22:43</var> UTC 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. Creating, viewing, and replying to pull request comments was unaffected, and other Copilot functionality continued to operate normally. The impact was limited to @copilot mentions on pull request comments not triggering Copilot coding agent runs, and to some downstream systems not receiving new pull request comment events during the impact window. The cause was a serialization error that prevented pull request comment events from being published to downstream consumers, including the Copilot coding agent. This was related to the same class of issue as incident #4295 on April 20, affecting a another event type. We mitigated the incident by deploying a fix that restored event publishing, after which the Copilot coding agent and other downstream consumers resumed processing pull request comment events normally. We are working to complete our audit of related event schemas, migrate remaining consumers to use the updated identifier fields, and improve monitoring to detect drops in publishing on critical event topics, to reduce our time to detection and mitigation of issues like this one in the future.Apr <var data-var='date'>22</var>, <var data-var='time'>22:09</var> UTC Update - We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.Apr <var data-var='date'>22</var>, <var data-var='time'>20:37</var> 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 <var data-var='date'>22</var>, <var data-var='time'>20:02</var> 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 <var data-var='date'>22</var>, <var data-var='time'>19:55</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>22</var>, <var data-var='time'>19:53</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Apr <var data-var='date'>22</var>, <var data-var='time'>19:18</var> UTC Resolved - On April 22, 2026, between 15:16 UTC and 19:18 UTC, users experienced errors when interacting with Copilot Chat on github.com and Copilot Cloud Agent. During this time, users were unable to use Copilot Chat or Copilot Cloud Agent. Copilot Memory (in preview) was not available to Copilot agent sessions during this time. The issue was caused by an infrastructure configuration change that resulted in connectivity issues with our databases. The team identified the cause and restored connectivity to the database. Copilot Chat and Cloud Agent for github.com were restored by 18:16 UTC. Remaining regional deployments were restored incrementally, with full resolution at 19:18 UTC. We have taken steps to prevent similar infrastructure changes from causing these kinds of database operations in the future.Apr <var data-var='date'>22</var>, <var data-var='time'>18:05</var> UTC Update - Copilot cloud agent and chat are mitigated for github.com.Apr <var data-var='date'>22</var>, <var data-var='time'>17:49</var> UTC Update - We are now seeing recovery for Copilot cloud agent.Apr <var data-var='date'>22</var>, <var data-var='time'>17:40</var> UTC Update - Mitigation is progressing for Copilot chat and cloud agent recovery.Apr <var data-var='date'>22</var>, <var data-var='time'>16:58</var> UTC Update - Mitigation is progressing for Copilot chat and cloud agent.Apr <var data-var='date'>22</var>, <var data-var='time'>16:24</var> UTC Update - We continue to work on mitigation for Copilot chat and cloud agent.Apr <var data-var='date'>22</var>, <var data-var='time'>15:43</var> 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 <var data-var='date'>22</var>, <var data-var='time'>15:35</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with Copilot chat and Copilot Coding Agent

Apr <var data-var='date'>22</var>, <var data-var='time'>01:24</var> UTC Resolved - On April 21, 2026, between 13:35 UTC and 01:24 UTC the following day the projects service was degraded. During this time period, projects may have been out of sync and users may have experienced delays in changes to projects and their items. Delays in reflected changes peaked at approximately 45 minutes. The delays were caused by serialization errors that failed events and triggered a flood of resyncs, overloading our event processing layers. We mitigated the incident by speeding up processing time for incoming changes and otherwise waiting for all changes to be processed. We are working to increase our capacity for processing updates to projects to reduce our time to mitigation of issues like this one in the future.Apr <var data-var='date'>22</var>, <var data-var='time'>00:00</var> 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 <var data-var='date'>21</var>, <var data-var='time'>22:49</var> 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 <var data-var='date'>21</var>, <var data-var='time'>21:15</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>21</var>, <var data-var='time'>19:41</var> 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 <var data-var='date'>21</var>, <var data-var='time'>17:21</var> UTC Update - The queues are continuing to decrease and we are working to accelerate the rate of processing through the queues.Apr <var data-var='date'>21</var>, <var data-var='time'>16:45</var> 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 <var data-var='date'>21</var>, <var data-var='time'>16:18</var> 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 <var data-var='date'>21</var>, <var data-var='time'>15:42</var> 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 <var data-var='date'>21</var>, <var data-var='time'>15:07</var> 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 <var data-var='date'>21</var>, <var data-var='time'>15:03</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with projects service

Apr <var data-var='date'>21</var>, <var data-var='time'>05:04</var> UTC 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 <var data-var='date'>21</var>, <var data-var='time'>04:18</var> UTC Update - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>21</var>, <var data-var='time'>03:10</var> 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 <var data-var='date'>20</var>, <var data-var='time'>21:36</var> UTC Update - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>20</var>, <var data-var='time'>18:21</var> UTC Update - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>20</var>, <var data-var='time'>18:20</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>20</var>, <var data-var='time'>18:20</var> 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 <var data-var='date'>20</var>, <var data-var='time'>18:08</var> UTC Update - A deployment to fix this issue of new issues not showing up in projects is underway.Apr <var data-var='date'>20</var>, <var data-var='time'>17:32</var> UTC Update - We continue to work on mitigation regarding new issues not showing on project boards.Apr <var data-var='date'>20</var>, <var data-var='time'>16:48</var> UTC Update - We continue to work on mitigation regarding new issues not showing on project boards.Apr <var data-var='date'>20</var>, <var data-var='time'>16:16</var> 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 <var data-var='date'>20</var>, <var data-var='time'>15:20</var> UTC Update - We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.Apr <var data-var='date'>20</var>, <var data-var='time'>14:38</var> UTC Update - We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.Apr <var data-var='date'>20</var>, <var data-var='time'>13:57</var> 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 <var data-var='date'>20</var>, <var data-var='time'>13:28</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Partial degradation for code scanning default setup and for code quality

Apr <var data-var='date'>17</var>, <var data-var='time'>15:18</var> UTC 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 <var data-var='date'>17</var>, <var data-var='time'>15:18</var> UTC Monitoring - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>17</var>, <var data-var='time'>15:08</var> 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 <var data-var='date'>17</var>, <var data-var='time'>14:57</var> 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 <var data-var='date'>17</var>, <var data-var='time'>14:56</var> UTC Update - Issues is experiencing degraded performance. We are continuing to investigate.Apr <var data-var='date'>17</var>, <var data-var='time'>14:56</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Apr <var data-var='date'>16</var>, <var data-var='time'>18:28</var> UTC 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 <var data-var='date'>16</var>, <var data-var='time'>18:22</var> UTC Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>16</var>, <var data-var='time'>16:37</var> UTC Update - Our provider is implementing a mitigation and we are seeing signs of recovery.Apr <var data-var='date'>16</var>, <var data-var='time'>15:49</var> UTC Update - We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.Apr <var data-var='date'>16</var>, <var data-var='time'>15:41</var> UTC Update - Codespaces is experiencing degraded availability. We are continuing to investigate.Apr <var data-var='date'>16</var>, <var data-var='time'>15:08</var> 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 <var data-var='date'>16</var>, <var data-var='time'>15:06</var> UTC Investigating - We are investigating reports of degraded performance for Codespaces

Incident with Codespaces

Apr <var data-var='date'>14</var>, <var data-var='time'>06:08</var> UTC 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 <var data-var='date'>14</var>, <var data-var='time'>06:07</var> 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 <var data-var='date'>14</var>, <var data-var='time'>06:07</var> UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.Apr <var data-var='date'>14</var>, <var data-var='time'>04:40</var> 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 <var data-var='date'>14</var>, <var data-var='time'>03:47</var> 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 <var data-var='date'>14</var>, <var data-var='time'>02:40</var> UTC Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.Apr <var data-var='date'>14</var>, <var data-var='time'>02:37</var> UTC Update - Degradation of Service - Insights PageApr <var data-var='date'>14</var>, <var data-var='time'>01:57</var> UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Is Github down?

Github status is UP

Lastest published events

Incident with CodeQL, Webhooks, Notifications, and Slack Integration

Incident with high errors on Git Operations

CCR and CCA failing to start for PR comments

Github Services, Components and Regions

Recent Github events

Incident with CodeQL, Webhooks, Notifications, and Slack Integration

Incident with high errors on Git Operations

CCR and CCA failing to start for PR comments

Incident with Pull Requests

Disruption with some GitHub services

Incident with Actions, we are investigating reports of degraded availability

Get your FREE account now,
5 monitors included!

Is Github down?

Github status is UP

Lastest published events

Incident with CodeQL, Webhooks, Notifications, and Slack Integration

Incident with high errors on Git Operations

CCR and CCA failing to start for PR comments

Github Services, Components and Regions

Recent Github events

Incident with CodeQL, Webhooks, Notifications, and Slack Integration

Incident with high errors on Git Operations

CCR and CCA failing to start for PR comments

Incident with Pull Requests

Disruption with some GitHub services

Incident with Actions, we are investigating reports of degraded availability

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!