GitHub Status

Mar 3, 2026

Delayed visibility of newly added issues on project boards

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 3, 05:54 UTC

Update - This incident has been resolved. Project board updates are now processing in near-real-time.
Mar 3, 05:53 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:36 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, 04:17 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, 03:22 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, 02:27 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, 01:40 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:52 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 3, 00:05 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:46 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:12 UTC

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

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

Mar 2, 2026

Incident with Pull Requests /pulls

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 2, 22:04 UTC

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

Update - We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
Mar 2, 21:04 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, 20:02 UTC

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

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

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

Incident with Copilot agent sessions

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.
Feb 27, 23:49 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:45 UTC

Update - We are investigating networking issues with some requests to our models.
Feb 27, 23:35 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
Feb 27, 23:18 UTC

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

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:04 UTC

Update - We have cleared all caches and everything is operating normally.
Feb 27, 06:03 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, 05:21 UTC

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

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

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

High latency on webhook API requests

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 27, 00:04 UTC

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

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

Feb 26, 2026

Incident with Copilot

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, 11:06 UTC

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

Feb 25, 2026

Incident with Copilot Agent Sessions impacting CCA/CCR

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.
Feb 25, 16:44 UTC

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

Feb 24, 2026

Code search experiencing degraded performance

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:46 UTC

Update - We have identified a cause for the latency and timeouts and have implemented a fix. We are observing initial recovery now.
Feb 24, 00:38 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, 23:10 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, 22:22 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, 21:18 UTC

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

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

Feb 23, 2026

Incident with Issues and Pull Requests Search

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:30 UTC

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

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

Incident with Actions

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.
Feb 23, 17:03 UTC

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

Incident with Copilot

Resolved - On February 23, 2026, between 14:45 UTC and 16:19 UTC, the Copilot service was degraded for Claude Haiku 4.5 model. On average, 6% of the requests to this model failed due to an issue with an upstream provider. During this period, automated model degradation notifications directed affected users to alternative models. No other models were impacted. The upstream provider identified and resolved the issue on their end.
We are working to improve automatic model failover mechanisms to reduce our time to mitigation of issues like this one in the future.
Feb 23, 16:19 UTC

Update - Copilot is operating normally.
Feb 23, 15:59 UTC

Update - The issues with our upstream model provider have been resolved, and Haiku 4.5 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.
Feb 23, 15:59 UTC

Update - Our provider has recovered and we are not seeing errors but we are awaiting a signal from them that the issue will not regress before we go green.
Feb 23, 15:13 UTC

Update - We are experiencing degraded availability for the Haiku 4.5 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.

Other models are available and working as expected.
Feb 23, 14:56 UTC

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

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026

Extended job start delays for larger hosted runners

Resolved - On February 20, 2026, between 17:45 UTC and 20:41 UTC, 4.2% of workflows running on GitHub Larger Hosted Runners were delayed by an average of 18 minutes. Standard, Mac, and Self-Hosted Runners were not impacted.

The delays were caused by communication failures between backend services for one deployment of larger runners. Those failures prevented expected automated scaling and provisioning of larger hosted runner capacity within that deployment. This was mitigated when the affected infrastructure was recycled, larger runner pools in the affected deployment successfully scaled up, and queued jobs processed.

We are working to improve the time to detect and diagnose this class of failures and improve the performance of recovery mechanisms for this degraded network state. In addition, we have architectural changes underway that will enable other deployments to pick up work in similar situations, so there is no customer impact due to deployment-specific infrastructure issues like this.
Feb 20, 20:41 UTC

Update - The team continues to investigate issues with some larger runner jobs being queued for a long time. We are though seeing improvement in the queue times. We will continue providing updates on the progress towards mitigation.
Feb 20, 20:36 UTC

Update - We are investigating reports of degraded performance for Larger Hosted Runners
Feb 20, 20:01 UTC

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

Incident with Copilot GPT-5.1-Codex

Resolved - On February 20, 2026, between 07:30 UTC and 11:21 UTC, the Copilot service experienced a degradation of the GPT 5.1 Codex model. During this time period, users encountered a 4.5% error rate when using this model. No other models were impacted.
The issue was resolved by a mitigation put in place by the external model provider. GitHub is working with the external model provider to further improve the resiliency of the service to prevent similar incidents in the future.
Feb 20, 11:41 UTC

Update - The issues with our upstream model provider have been resolved, and GPT 5.1 Codex is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains].
We will continue monitoring to ensure stability, but mitigation is complete.
Feb 20, 11:19 UTC

Update - We are still experiencing degraded availability for the GPT 5.1 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.

Feb 20, 10:36 UTC

Update - We are experiencing degraded availability for the GPT 5.1 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.
Other models are available and working as expected.
Feb 20, 10:02 UTC

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

Feb 19, 2026

No incidents reported.

Feb 18, 2026

Degraded performance in merge queue

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

Update - We have seen significant recovery in merge queue we are continuing to monitor for any other degraded services.
Feb 18, 19:18 UTC

Update - We are investigating reports of issues with merge queue. We will continue to keep users updated on progress towards mitigation.
Feb 18, 18:27 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 18, 18:26 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 18, 18:25 UTC

Feb 17, 2026

Intermittent authentication failures on GitHub

Resolved - On February 17, 2026, between 17:07 UTC and 19:06 UTC, some customers experienced intermittent authentication failures affecting GitHub Actions, parts of Git operations, and other authentication-dependent requests. On average, the Actions error rate was approximately 0.6% of affected API requests. Git operations ssh read error rate was approximately 0.29%, while ssh write and http operations were not impacted. During the incident, a subset of requests failed due to token verification lookups intermittently failing, leading to 401 errors and degraded reliability for impacted workflows.

The issue was caused by elevated replication lag in the token verification database cluster. In the days leading up to the incident, the token store’s write volume grew enough to exceed the cluster’s available capacity. Under peak load, older replica hosts were unable to keep up, replica lag increased, and some token lookups became inconsistent, resulting in intermittent authentication failures.

We mitigated the incident by adjusting the database replica topology to route reads away from lagging replicas and by adding/bringing additional replica capacity online. Service health improved progressively after the change, with GitHub Actions recovering by ~19:00 UTC and the incident resolved at 19:06 UTC.

We are working to prevent recurrence by improving the resilience and scalability of our underlying token verification data stores to better handle continued growth.
Feb 17, 19:06 UTC

Update - We are continuing to monitor the mitigation and continuing to see signs of recovery.
Feb 17, 18:55 UTC

Update - We have rolled out a mitigation and are seeing signs of recovery and are continuing to monitor.
Feb 17, 18:18 UTC

Update - We have identified a low rate of authentication failures affecting GitHub App server to server tokens, GitHub Actions authentication tokens, and git operations. Some customers may experience intermittent API request failures when using these tokens. We believe we've identified the cause and are working to mitigate impact.
Feb 17, 17:46 UTC

Investigating - We are investigating reports of degraded performance for Actions and Git Operations
Feb 17, 17:46 UTC

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents