GitHub Status - Incident History

Degraded performance for various services

2026-03-13T16:15:33Z

Mar 13, 16:15 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.

Mar 13, 16:02 UTC
Update - We have deployed mitigations and are actively monitoring for recovery. We'll post another update by 17:00 UTC.

Mar 13, 15:47 UTC
Update - We are investigating intermittent performance degradation affecting Actions, Feeds, Issues, Package Registry, Profiles, Registry Metadata, Star, and User Dashboard. Users may experience elevated error rates and slower response times when accessing these services. We have identified a potential cause and are implementing mitigations to restore normal service. We'll post another update by 16:15 UTC.

Mar 13, 15:20 UTC
Update - Packages is experiencing degraded performance. We are continuing to investigate.

Mar 13, 15:14 UTC
Update - We are investigating reports of issues with service(s): Actions, Feeds, Issues, Profiles, Registry Metadata, Star, User Dashboard. We will continue to keep users updated on progress towards mitigation.

Mar 13, 15:12 UTC
Investigating - We are investigating reports of degraded performance for Actions and Issues

Degraded Codespaces experience

2026-03-12T18:53:33Z

Mar 12, 18:53 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.

Mar 12, 17:59 UTC
Update - Codespaces IPs are no longer being blocked from Visual Studio Marketplace operations and we are monitoring for full recovery

Mar 12, 17:20 UTC
Update - We're seeing intermittent failures downloading from the extension marketplace from codespaces, caused by IP blocks for some codespaces. We're working to remove those blocks.

Mar 12, 16:09 UTC
Update - We're seeing intermittent failures downloading from the extension marketplace from codespaces and are investigating.

Mar 12, 15:08 UTC
Update - We're seeing partial recovery for the issue affecting extension installation in newly created Codespaces. Some users may still experience degraded functionality where extensions hit errors. The team continues to investigate the root cause while monitoring the recovery.

Mar 12, 14:29 UTC
Update - We have deployed a fix for the issue affecting extension installation in newly created Codespaces. New Codespaces are now being created with working extensions. We'll post another update by 15:30 UTC.

Mar 12, 13:50 UTC
Update - We are continuing to investigate an issue where extensions fail to install in newly created Codespaces. Users can create and access Codespaces, but extensions will not be operational, resulting in a degraded experience. The team is working on a fix. All newly created Codespaces are affected. We'll post another update by 15:00 UTC.

Mar 12, 13:07 UTC
Update - We're investigating an issue where extensions fail to install in newly created Codespaces. Users can still create and access Codespaces, but extensions will not be operational, resulting in a degraded development experience. Our team is actively working to identify and resolve the root cause. We'll post another update by 14:00 UTC.

Mar 12, 13:06 UTC
Investigating - We are investigating reports of degraded performance for Codespaces

Actions failures to download (401 Unauthorized)

2026-03-12T06:02:07Z

Mar 12, 06:02 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.

Mar 12, 06:02 UTC
Monitoring - Actions is operating normally.

Mar 12, 05:40 UTC
Update - We are continuing investigation of reports of degraded performance for Actions and GitHub Apps

Mar 12, 04:46 UTC
Investigating - We are investigating reports of degraded performance for Actions

Disruption with some GitHub services

2026-03-12T02:45:55Z

Mar 12, 02:45 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.

Mar 12, 02:44 UTC
Update - We've identified the root cause and are working on resolving the underlying issue. Some users may have encountered intermittent failures and errors. We're continuing to see reduced error rates.

Mar 12, 02:13 UTC
Update - We are investigating elevated error rates. Error rates are now decreasing and we're continuing to monitor the situation.

Mar 12, 01:54 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Degraded experience with Copilot Code Review

2026-03-11T15:53:15Z

Mar 11, 15:53 UTC
Resolved - On March 11, 2026, between 13:00 UTC and 15:23 UTC the Copilot Code Review service was degraded and experienced longer than average review times. On average, Copilot Code Review requests took 4 minutes and peaked at just under 8 minutes. This was due to hitting worker capacity limits and CPU throttling. We mitigated the incident by increasing partitions, and we are improving our resource monitoring to identify potential issues sooner.

Mar 11, 15:53 UTC
Update - Copilot Code Review queue processing has returned to normal levels.

Mar 11, 15:31 UTC
Update - We experienced degraded performance with Copilot Code Review starting at 14:01 UTC. Customers experienced extended review times and occasional failures. Some extended processing times may continue briefly. We are monitoring for full recovery. We'll post another update by 16:30 UTC.

Mar 11, 14:28 UTC
Monitoring - We are investigating degraded performance with Copilot Code Review. Customers may experience extended review times or occasional failures. We are seeing signs of improvement as our team works to restore normal service. We'll post another update by 15:30 UTC.

Mar 11, 14:25 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with API Requests

2026-03-11T15:02:23Z

Mar 11, 15:02 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.

Mar 11, 15:02 UTC
Update - We are investigating elevated timeouts that affected GitHub API requests. The incident began at 14:37 UTC. Some users experienced slower response times and request failures. System metrics have returned to normal levels, and we are now investigating the root cause to prevent recurrence.

Mar 11, 14:37 UTC
Investigating - We are investigating reports of degraded performance for API Requests

Incident with Webhooks

2026-03-09T17:03:40Z

Mar 9, 17:03 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.

Mar 9, 17:03 UTC
Update - Webhooks is operating normally.

Mar 9, 15:56 UTC
Update - We are experiencing latency on the API and UI endpoints. We are working to resolve the issue.

Mar 9, 15:50 UTC
Investigating - We are investigating reports of degraded performance for Webhooks

Incident with Codespaces

2026-03-09T03:51:42Z

Mar 9, 03:51 UTC
Resolved - On March 9, 2026, between 01:23 UTC and 03:25 UTC, users attempting to create or resume codespaces in the Australia East region experienced elevated failures, peaking at a 100% failure rate for this region. Codespaces in other regions were not affected.

The create and resume failures were caused by degraded network connectivity between our control plane services and the VMs hosting the codespaces. This was resolved by redirecting traffic to an alternate site within the region. While we are addressing the core network infrastructure issue, we have also improved our observability of components in this area to improve detection. This will also enable our existing automated failovers to cover this failure mode. These changes will prevent or significantly reduce the time any similar incident causes user impact.

Mar 9, 03:51 UTC
Update - This incident has been resolved. New Codespace creation requests are now completing successfully.

Mar 9, 03:32 UTC
Update - We are seeing recovery, with the failure rate for new Codespace creation requests dropping from 5% to about 3%.

Mar 9, 03:04 UTC
Update - We are seeing about 5% of new Codespace creation requests failing. We are investigating the root cause and identifying the impacted regions.

Mar 9, 03:04 UTC
Investigating - We are investigating reports of degraded performance for Codespaces

Incident with Webhooks

2026-03-06T23:28:13Z

Mar 6, 23:28 UTC
Resolved - On March 6, 2026, between 16:16 UTC and 23:28 UTC the Webhooks service was degraded and some users experienced intermittent errors when accessing webhook delivery histories, retrying webhook deliveries, and listing webhooks via the UI and API. On average, the error rate was 0.57% and peaked at approximately 2.73% of requests to the service. This was due to unhealthy infrastructure affecting a portion of webhook API traffic.

We mitigated the incident by redeploying affected services, after which service health returned to normal.

We are working to improve detection of unhealthy infrastructure and strengthen service safeguards to reduce time to detection and mitigation of issues like this one in the future.

Mar 6, 23:28 UTC
Update - Webhooks is operating normally.

Mar 6, 23:26 UTC
Update - We have deployed a fix and are observing a full recovery. The affected endpoint was the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. We will continue monitoring to confirm stability.

Mar 6, 22:35 UTC
Update - We are preparing a new mitigation for the issue affecting the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. Overall impact remains low, with under 1% of requests failing for a subset of customers.

Mar 6, 21:34 UTC
Update - The previous mitigation did not resolve the issue. We are investigating further. The affected endpoint is the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. Overall impact remains low, with under 1% of requests failing for a subset of customers.

Mar 6, 20:18 UTC
Update - We have deployed a fix for the issue causing some users to experience intermittent failures when accessing the Webhooks API and configuration pages. We are monitoring to confirm full recovery.

Mar 6, 19:39 UTC
Update - We continue working on mitigations to restore service.

Mar 6, 19:07 UTC
Update - We continue working on mitigations to restore service.

Mar 6, 18:39 UTC
Update - We continue working on mitigations to restore service.

Mar 6, 18:07 UTC
Update - We continue working on mitigations to restore full service.

Mar 6, 17:43 UTC
Update - Our engineers have identified the root cause and are actively implementing mitigations to restore full service.

Mar 6, 17:19 UTC
Update - This problem is impacting less than 1% of UI and webhook API calls.

Mar 6, 17:12 UTC
Update - We are investigating an issue affecting a subset of customers experiencing errors when viewing webhook delivery histories and retrying webhook deliveries. UI and webhook API is impacted. Engineers have identified the cause and are actively working on mitigation.

Mar 6, 16:58 UTC
Investigating - We are investigating reports of degraded performance for Webhooks

Actions is experiencing degraded availability

2026-03-05T23:55:20Z

Mar 5, 23:55 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.

Mar 5, 23:40 UTC
Update - We are close to full recovery. Actions and dependent services should be functioning normally now.

Mar 5, 23:37 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Mar 5, 23:15 UTC
Update - Actions and dependent services, including Pages, are recovering.

Mar 5, 23:00 UTC
Update - We applied a mitigation and we should see a recovery soon.

Mar 5, 22:54 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.

Mar 5, 22:53 UTC
Investigating - We are investigating reports of degraded performance for Actions

Multiple services are affected, service degradation

2026-03-05T19:30:54Z

Mar 5, 19:30 UTC
Resolved - On Mar 5, 2026, between 16:24 UTC and 19:30 UTC, Actions was degraded. During this time, 95% of workflow runs failed to start within 5 minutes with an average delay of 30 minutes and 10% workflow runs failed with an infrastructure error. This was due to Redis infrastructure updates that were being rolled out to production to improve our resiliency. These changes introduced a set of incorrect configuration change into our Redis load balancer causing internal traffic to be routed to an incorrect host leading to two incidents.

We mitigated this incident by correcting the misconfigured load balancer. Actions jobs were running successfully starting at 17:24 UTC. The remaining time until we closed the incident was burning through the queue of jobs.

We immediately rolled back the updates that were a contributing factor and have frozen all changes in this area until we have completed follow-up work from this. We are working to improve our automation to ensure incorrect configuration changes are not able to propagate through our infrastructure. We are also working on improved alerting to catch misconfigured load balancers before it becomes an incident. Additionally, we are updating the Redis client configuration in Actions to improve resiliency to brief cache interruptions.

Mar 5, 19:17 UTC
Update - Webhooks is operating normally.

Mar 5, 19:05 UTC
Update - Actions is operating normally.

Mar 5, 18:59 UTC
Update - Actions is now fully recovered.

Mar 5, 18:15 UTC
Update - The queue of requested Actions jobs continues to make progress. Job delays are now approximately 6 minutes and continuing to decrease.

Mar 5, 17:48 UTC
Update - We are back to queueing Actions workflow runs at nominal rates and we are monitoring the clearing of queued runs during the incident.

Mar 5, 17:25 UTC
Update - We have applied mitigations for connection failures across backend resources and we are observing a recovery in queueing Actions workflow runs.

Mar 5, 16:52 UTC
Update - We are observing delays in queuing Actions workflow runs. We’re still investigating the causes of these delays.

Mar 5, 16:47 UTC
Update - Webhooks is experiencing degraded availability. We are continuing to investigate.

Mar 5, 16:41 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.

Mar 5, 16:35 UTC
Investigating - We are investigating reports of degraded performance for Actions

Disruption with some GitHub services

2026-03-05T01:30:37Z

Mar 5, 01:30 UTC
Resolved - On March 5, 2026, between 12:53 UTC and 13:35 UTC, the Copilot mission control service was degraded. This resulted in empty responses returned for users' agent session lists across GitHub web surfaces. Impacted users were unable to see their lists of current and previous agent sessions in GitHub web surfaces. This was caused by an incorrect database query that falsely excluded records that have an absent field.

We mitigated the incident by rolling back the database query change. There were no data alterations nor deletions during the incident.

To prevent similar issues in the future, we're improving our monitoring depth to more easily detect degradation before changes are fully rolled out.

Mar 5, 01:30 UTC
Update - Copilot coding agent mission control is fully restored. Tasks are now listed as expected.

Mar 5, 01:21 UTC
Update - Users were temporarily unable to see tasks listed in mission control surfaces. The ability to submit new tasks, view existing tasks via direct link, or manage tasks was unaffected throughout. A revert is currently being deployed and we are seeing recovery.

Mar 5, 01:13 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Some OpenAI models degraded in Copilot

2026-03-05T01:13:31Z

Mar 5, 01:13 UTC
Resolved - On March 5th, 2026, between approximately 00:26 and 00:44 UTC, the Copilot service experienced a degradation of the GPT 3.5 Codex model due to an issue with our upstream provider. Users encountered elevated error rates when using GPT 3.5 Codex, impacting approximately 30% of requests. No other models were impacted.

The issue was resolved by a mitigation put in place by our provider.

Mar 5, 01:13 UTC
Update - The issues with our upstream model provider have been resolved, and gpt-5.3-codex is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete.

Mar 5, 00:53 UTC
Update - We are experiencing degraded availability for the gpt-5.3-codex model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

Mar 5, 00:47 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Claude Opus 4.6 Fast not appearing for some Copilot users

2026-03-03T21:11:30Z

Mar 3, 21:11 UTC
Resolved - On March 3, 2026, between 19:44 UTC and 21:05 UTC, some GitHub Copilot users reported that the Claude Opus 4.6 Fast model was no longer available in their IDE model selection. After investigation, we confirmed that this was caused by enterprise administrators adjusting their organization's model policies, which correctly removed the model for users in those organizations. No users outside the affected organizations lost access.

We confirmed that the Copilot settings were functioning as designed, and all expected users retained access to the model. The incident was resolved once we verified that the change was intentional and no platform regression had occurred.

Mar 3, 21:05 UTC
Update - We believe that all expected users still have access to Claude Opus 4.6. We confirm that no users have lost access.

Mar 3, 20:31 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Incident with all GitHub services

2026-03-03T20:09:16Z

Mar 3, 20:09 UTC
Resolved - On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures reached approximately 40%. During the same period, approximately 43% of GitHub API requests failed. Git operations over HTTP had an error rate of approximately 6%, while SSH was not impacted. GitHub Copilot requests had an error rate of approximately 21%. GitHub Actions experienced less than 1% impact.

This incident shared the same underlying cause as an incident in early February where we saw a large volume of writes to the user settings caching mechanism. While deploying a change to reduce the burden of these writes, a bug caused every user’s cache to expire, get recalculated, and get rewritten. The increased load caused replication delays that cascaded down to all affected services. We mitigated this issue by immediately rolling back the faulty deployment.

We understand these incidents disrupted the workflows of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, we acknowledge we have more work to do. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps:

- We have added a killswitch and improved monitoring to the caching mechanism to ensure we are notified before there is user impact and can respond swiftly.
- We are moving the cache mechanism to a dedicated host, ensuring that any future issues will solely affect services that rely on it.

Mar 3, 20:06 UTC
Update - We're seeing recovery across all services. We're continuing to monitor for full recovery.

Mar 3, 19:55 UTC
Update - Actions is operating normally.

Mar 3, 19:54 UTC
Update - Git Operations is operating normally.

Mar 3, 19:36 UTC
Update - Git Operations is experiencing degraded availability. We are continuing to investigate.

Mar 3, 19:33 UTC
Update - We are seeing recovery across multiple services. Impact is mostly isolated to git operations at this point, we continue to investigate

Mar 3, 19:31 UTC
Update - Copilot is operating normally.

Mar 3, 19:31 UTC
Update - Pull Requests is operating normally.

Mar 3, 19:28 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:27 UTC
Update - Issues is operating normally.

Mar 3, 19:25 UTC
Update - Webhooks is operating normally.

Mar 3, 19:25 UTC
Update - Codespaces is operating normally.

Mar 3, 19:24 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:23 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:17 UTC
Update - We've identified the issue and have applied a mitigation. We're seeing recovery of services. We continue to montitor for full recovery.

Mar 3, 19:15 UTC
Update - API Requests is operating normally.

Mar 3, 19:14 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:11 UTC
Update - Codespaces is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:05 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.

Mar 3, 19:04 UTC
Update - Webhooks is experiencing degraded availability. We are continuing to investigate.

Mar 3, 19:03 UTC
Update - We're seeing some service degradation across GitHub services. We're currently investigating impact.

Mar 3, 19:02 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:00 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Mar 3, 19:00 UTC
Update - API Requests is experiencing degraded availability. We are continuing to investigate.

Mar 3, 18:59 UTC
Investigating - We are investigating reports of degraded availability for Actions, Copilot and Issues

Delayed visibility of newly added issues on project boards

2026-03-03T05:54:17Z

Mar 3, 05:54 UTC
Resolved - Between March 2, 21:42 UTC and March 3, 05:54 UTC project board updates, including adding new issues, PRs, and draft items to boards, were delayed from 30 minutes to over 2 hours, as a large backlog of messages accumulated in the Projects data denormalization pipeline.

The incident was caused by an anomalously large event that required longer processing time than expected. Processing this message exceeded the Kafka consumer heartbeat timeout, triggering repeated consumer group rebalances. As a result, the consumer group was unable to make forward progress, creating head-of-line blocking that delayed processing of subsequent project board updates.

We mitigated the issue by deploying a targeted fix that safely bypassed the offending message and allowed normal message consumption to resume. Consumer group stability recovered at 04:10 UTC, after which the backlog began draining. All queued messages were fully processed by 05:53 UTC, returning project board updates to normal processing latency.

We have identified several follow-up improvements to reduce the likelihood and impact of similar incidents in the future, including improved monitoring and alerting, as well as introducing limits for unusually large project events.

Mar 3, 05:53 UTC
Update - This incident has been resolved. Project board updates are now processing in near-real-time.

Mar 3, 04:36 UTC
Update - The backlog of delayed updates is expected to fully clear within approximately 1 hour, after which project board updates will return to near-real-time.

Mar 3, 04:17 UTC
Update - The fix has been deployed and processing speeds have returned to normal. There is a backlog of delayed updates that will continue to be worked through — we're estimating how long that will take and will provide an update in the next 60 minutes.

Mar 3, 03:22 UTC
Update - The fix is still building and is expected to deploy within 60 minutes. The current delay for GitHub Projects updates has increased to up to 5 hours.

Mar 3, 02:27 UTC
Update - We're deploying a fix targeting the increased delay in GitHub Projects updates. The rollout should complete within 60 minutes. If successful, the current delay of up to 4 hours should begin to decrease.

Mar 3, 01:40 UTC
Update - The delay for project board updates has increased to up to 3 hours. We've identified a potential cause and are working on remediation.

Mar 3, 00:52 UTC
Update - Project board updates — including adding issues, pull requests, and changing fields such as "Status" — are currently delayed by 1–2 hours. Normal behavior is near-real-time. We're actively investigating the root cause.

Mar 3, 00:05 UTC
Update - The impact extends beyond adding issues to project boards. Adding pull requests and updating fields such as "Status" may also be affected. We're continuing to investigate the root cause.

Mar 2, 23:46 UTC
Update - Newly added issues are taking 30–60 minutes to appear on project boards, compared to the normal near-real-time behavior. We're investigating the root cause and possible mitigations.

Mar 2, 23:12 UTC
Update - Newly added issues can take up to 30 minutes to appear on project boards. We're investigating the cause of this delay.

Mar 2, 23:11 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.

Mar 2, 23:10 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with Pull Requests /pulls

2026-03-02T22:04:27Z

Mar 2, 22:04 UTC
Resolved - On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.

This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.

We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.

Mar 2, 22:04 UTC
Update - The issue on https://github.com/pulls is now fully resolved. All tabs are working again.

Mar 2, 21:04 UTC
Update - We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.

Mar 2, 20:02 UTC
Update - We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.

Mar 2, 19:23 UTC
Update - We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.

Mar 2, 19:11 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests

Incident with Copilot agent sessions

2026-02-27T23:49:05Z

Feb 27, 23:49 UTC
Resolved - On February 27, 2026, between 22:53 UTC and 23:46 UTC, the Copilot coding agent service experienced elevated errors and degraded functionality for agent sessions. Approximately 87% of attempts to start or interact with agent sessions encountered errors during this period.

This was due to an expired authentication credential for an internal service component, which prevented Copilot agent session operations from completing successfully.

We mitigated the incident by rotating the expired credential and deploying the updated configuration to production. Services began recovering within minutes of the fix being deployed.

We are working to improve automated credential rotation coverage across all Copilot service components, add proactive alerting for credentials approaching expiration, and validate configuration consistency to reduce our time to detection and mitigation of issues like this one in the future.

Feb 27, 23:45 UTC
Update - We have identified the cause of the elevated errors and are rolling out a fix to production. We are observing initial recovery in Copilot agent sessions.

Feb 27, 23:35 UTC
Update - We are investigating networking issues with some requests to our models.

Feb 27, 23:18 UTC
Update - We are investigating a spike in errors in Copilot agent sessions

Feb 27, 23:18 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Code view fails to load when content contains some non-ASCII characters

2026-02-27T06:04:02Z

Feb 27, 06:04 UTC
Resolved - Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the error rate was 0.014% and peaked at 0.06% of requests to the service. Affected users saw 404 errors when navigating to repository directories and files with non-ASCII names. This was due to a code change that altered how file and directory names were processed, which caused incorrectly formatted data to be stored in an application cache.

We mitigated the incident by deploying a fix that invalidated the affected cache entries and progressively rolling it out across all production environments.

We are working to improve our pre-production testing to cover non-ASCII character handling, establish better cache invalidation mechanisms, and enhance our monitoring to detect this type of failure mode earlier, to reduce our time to detection and mitigation of issues like this one in the future.

Feb 27, 06:03 UTC
Update - We have cleared all caches and everything is operating normally.

Feb 27, 05:21 UTC
Update - We have mitigated the issue but are working on invalidating caches in order to fix the issue for all impacted repos.

Feb 27, 04:17 UTC
Update - We have performed a mitigation but some repositories may still see issues. We are working on a full mitigation.

Feb 27, 03:28 UTC
Update - We are looking into recent code changes to mitigate the error loading some code view pages.

Feb 27, 03:08 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

High latency on webhook API requests

2026-02-27T00:04:01Z

Feb 27, 00:04 UTC
Resolved - Between February 26, 2026 UTC and February 27, 2026 UTC, customers hitting the webhooks delivery API may have experienced higher latency or failed requests. During the impact window, 0.82% of requests took longer than 3s and 0.004% resulted in a 500 error response.

Our monitors caught the impact on the individual backing data source, and we were able to attribute the degradation to a noisy neighbor effect due requests to a specific webhook generating excessive load on the API. The incident was mitigated once traffic from the specific hook decreased.

We have since added a rate limiter for this webhooks API to prevent similar spikes in usage impacting others and will further refine the rate limits for other webhook API routes to help prevent similar occurrences in the future.

Feb 27, 00:02 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.

Feb 27, 00:01 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with Copilot

2026-02-26T11:06:32Z

Feb 26, 11:06 UTC
Resolved - On February 26, 2026, between 09:27 UTC and 10:36 UTC, the GitHub Copilot service was degraded and users experienced errors when using Copilot features including Copilot Chat, Copilot Coding Agent and Copilot Code Review. During this time, 5-15% of affected requests to the service returned errors.

The incident was resolved by infrastructure rebalancing.

We are improving observability to detect capacity imbalances earlier and enhancing our infrastructure to better handle traffic spikes.

Feb 26, 11:06 UTC
Update - Copilot is operating normally.

Feb 26, 10:22 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Incident with Copilot Agent Sessions impacting CCA/CCR

2026-02-25T16:44:50Z

Feb 25, 16:44 UTC
Resolved - On February 25, 2026, between 15:05 UTC and 16:34 UTC, the Copilot coding agent service was degraded, resulting in errors for 5% of all requests and impacting users starting or interacting with agent sessions.

This was due to an internal service dependency running out of allocated resources (memory and CPU). We mitigated the incident by adjusting the resource allocation for the affected service, which restored normal operations for the coding agent service.

We are working to implement proactive monitoring for resource exhaustion across our services, review and update resource allocations, and improve our alerting capabilities to reduce our time to detection and mitigation of similar issues in the future.

Feb 25, 16:38 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Code search experiencing degraded performance

2026-02-24T00:46:29Z

Feb 24, 00:46 UTC
Resolved - Between 2026-02-23 19:10 and 2026-02-24 00:46 UTC, all lexical code search queries in GitHub.com and the code search API were significantly slowed, and during this incident, between 5 and 10% of search queries timed out. This was caused by a single customer who had created a network of hundreds of orchestrated accounts which searched with a uniquely expensive search query. This search query concentrated load on a single hot shard within the search index, slowing down all queries. After we identified the source of the load and stopped the traffic, latency returned to normal.

To avoid this situation occurring again in the future, we are making a number of improvements to our systems, including: improved rate limiting that accounts for highly skewed load on hot shards, improved system resilience for when a small number of shards time out, improved tooling to recognize abusive actors, and capabilities that will allow us to shed load on a single shard in emergencies.

Feb 24, 00:38 UTC
Update - We have identified a cause for the latency and timeouts and have implemented a fix. We are observing initial recovery now.

Feb 23, 23:10 UTC
Update - Customers using code search continue to see increased latency and timeout errors. We are working to mitigate issues on the affected shard.

Feb 23, 22:22 UTC
Update - Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are taking steps to isolate and mitigate the affected shard.

Feb 23, 21:18 UTC
Update - Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are continuing to investigate the cause and steps to mitigate.

Feb 23, 20:33 UTC
Update - We are continuing to investigate elevated latency and timeouts for code search.

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

Incident with Issues and Pull Requests Search

2026-02-23T21:30:42Z

Feb 23, 21:30 UTC
Resolved - On February 23, 2026, between 21:01 UTC and 21:30 UTC the Search service experienced degraded performance, resulting in an average of 3.5% of search requests for Issues and Pull Requests being rejected. During this period, updates to Issues and Pull Requests may not have been immediately reflected in search results.

During a routine migration, we observed a spike in internal traffic due to a configuration change in our search index. We were alerted to the increase in traffic as well as the increase in error rates and rolled back to the previous stable index.

We are working to enable more controlled traffic shifting when promoting a new index to allow us to detect potential limitations earlier and ensure these operations succeed in a more controlled manner.

Feb 23, 21:24 UTC
Update - Some customers are seeing timeout errors when searching for issues or pull requests. Team is currently investigating a fix.

Feb 23, 21:16 UTC
Investigating - We are investigating reports of degraded performance for Issues and Pull Requests

Incident with Actions

2026-02-23T17:03:56Z

Feb 23, 17:03 UTC
Resolved - On February 23, 2026, between 15:00 UTC and 17:00 UTC, GitHub Actions experienced degraded performance. During the time, 1.8% of Actions workflow runs experienced delayed starts with an average delay of 15 minutes. The issue was caused by a connection rebalancing event in our internal load balancing layer, which temporarily created uneven traffic distribution across sites and led to request throttling.

To prevent recurrence, we are tuning connection rebalancing behavior to spread client reconnections more gradually during load balancer reloads. We are also evaluating improvements to site-level traffic affinity to eliminate the uneven distribution at its source. We have overprovisioned critical paths to prevent any impact if a similar event occurs before those workstreams finish. Finally, we are enhancing our monitoring to detect capacity imbalances proactively.

Feb 23, 16:17 UTC
Investigating - We are investigating reports of degraded performance for Actions