GitHub Enterprise Cloud US Status - Incident History

US - Disruption with GHEC With Data Residency Signup

2025-10-22T17:35:48Z

Oct 22, 17:35 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.

Oct 22, 17:35 UTC
Update - We have now recovered and will resolve this incident.

Oct 22, 16:45 UTC
Update - We have applied a mitigation and are monitoring for recovery.

Oct 22, 14:33 UTC
Update - We have identified the problem and are working on a mitigation. We will provide further updates as we have them.

Oct 22, 14:03 UTC
Update - We are currently experiencing disruptions with the GHEC with Data Residency signup process. Some requests to provision new GHEC with Data Residency enterprises will not complete at this time. We are investigating and will provide further updates as we have more information

Oct 22, 13:56 UTC
Investigating - We are currently investigating this issue.

US - Disruption with push notifications

2025-10-17T14:12:45Z

Oct 17, 14:12 UTC
Resolved - On October 17th, 2025, between 12:51 UTC and 14:01 UTC, mobile push notifications failed to be delivered for a total duration of 70 minutes. This affected github.com and GitHub Enterprise Cloud in all regions. The disruption was related to an erroneous configuration change to cloud resources used for mobile push notification delivery.

We are reviewing our procedures and management of these cloud resources to prevent such an incident in the future.

Oct 17, 14:01 UTC
Update - We're investigating an issue with mobile push notifications. All notification types are affected, but notifications remain accessible in the app's inbox. For 2FA authentication, please open the GitHub mobile app directly to complete login.

Oct 17, 13:12 UTC
Investigating - We are currently investigating this issue.

US - Incident with Copilot

2025-10-03T03:47:29Z

Oct 3, 03:47 UTC
Resolved -

On October 3rd, between approximately 10:00 PM and 11:30 Eastern, the Copilot service experienced degradation due to an issue with our upstream provider. Users encountered elevated error rates when using the following Claude models: Claude Sonnet 3.7, Claude Opus 4, Claude Opus 4.1, Claude Sonnet 4, and Claude Sonnet 4.5. No other models were impacted.

The issue was mitigated by temporarily disabling affected endpoints while our provider resolved the upstream issue. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

Oct 3, 03:47 UTC
Update - 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.

Oct 3, 03:04 UTC
Update - The upstream provider is implementing a fix. Services are recovering. We are monitoring the situation.

Oct 3, 02:42 UTC
Update - We’re seeing degraded experience across Anthropic models. We’re working with our partners to restore service.

Oct 3, 02:41 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Degraded Gemini 2.5 Pro experience in Copilot

2025-10-02T22:33:22Z

Oct 2, 22:33 UTC
Resolved - Between October 1st, 2025 at 1 AM UTC and October 2nd, 2025 at 10:33 PM UTC, the Copilot service experienced a degradation of the Gemini 2.5 Pro model due to an issue with our upstream provider. Before 15:53 UTC on October 1st, users experienced higher error rates with large context requests while using Gemini 2.5 Pro. After 15:53 UTC and until 10:33 PM UTC on October 2nd, requests were restricted to smaller context windows when using Gemini 2.5. Pro. No other models were impacted.

The issue was resolved by a mitigation put in place by our provider. GitHub is collaborating with our provider to enhance communication and improve the ability to reproduce issues with the aim to reduce resolution time.

Oct 2, 22:26 UTC
Update - We have confirmed that the fix for the lower token input limit for Gemini 2.5 Pro is in place and are currently testing our previous higher limit to verify that customers will experience no further impact.

Oct 2, 17:13 UTC
Update - The underlying issue for the lower token limits for Gemini 2.5 Pro has been identified and a fix is in progress. We will update again once we have tested and confirmed that the fix is correct and globally deployed.

Oct 2, 02:52 UTC
Update - We are continuing to work with our provider to resolve the issue where some Copilot requests using Gemini 2.5 Pro return an error indicating a bad request due to exceeding the input limit size.

Oct 1, 18:16 UTC
Update - We are continuing to investigate and test solutions internally while working with our model provider on a deeper investigation into the cause. We will update again when we have identified a mitigation.

Oct 1, 17:37 UTC
Update - We are testing other internal mitigations so that we can return to the higher maximum input length. We are still working with our upstream model provider to understand the contributing factors for this sudden decrease in input limits.

Oct 1, 16:49 UTC
Update - We are experiencing a service regression for the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products. The maximum input length of Gemini 2.5 prompts been decreased. Long prompts or large context windows may result in errors. 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.

Oct 1, 16:43 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot

2025-09-29T19:12:42Z

Sep 29, 19:12 UTC
Resolved - On September 29, 2025, between 17:53 and 18:42 UTC, the Copilot service experienced a degradation of the Gemini 2.5 model due to an issue with our upstream provider. Approximately 24% of requests failed, affecting 56% of users during this period. No other models were impacted.

GitHub notified the upstream provider of the problem as soon as it was detected. The issue was resolved after the upstream provider rolled back a recent change that caused the disruption. GitHub will continue to enhance our monitoring and alerting systems to reduce the time it takes to detect and mitigate similar issues in the future.

Sep 29, 19:12 UTC
Update - The upstream model provided has resolved the issue and we are seeing full availability for Gemini 2.5 Pro and Gemini 2.0 Flash.

Sep 29, 18:40 UTC
Update - We are experiencing degraded availability for the Gemini 2.5 Pro & Gemini 2.0 Flash models 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.

Sep 29, 18:39 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-09-29T17:33:52Z

Sep 29, 17:33 UTC
Resolved - On September 29, 2025 between 16:26 UTC and 17:33 UTC the Copilot API experienced a partial degradation causing intermittent erroneous 404 responses for an average of 0.2% of GitHub MCP server requests, peaking at times around 2% of requests. The issue stemmed from an upgrade of an internal dependency which exposed a misconfiguration in the service.

We resolved the incident by rolling back the upgrade to address the misconfiguration. We fixed the configuration issue and will improve documentation and rollout process to prevent similar issues.

Sep 29, 17:28 UTC
Update - Customers are getting 404 responses when connecting to the GitHub MCP server. We have reverted a change we believe is contributing to the impact, and are seeing resolution in deployed environments.

Sep 29, 16:45 UTC
Investigating - We are currently investigating this issue.

US - Claude Opus 4 is experiencing degraded performance

2025-09-24T09:18:32Z

Sep 24, 09:18 UTC
Resolved - Anthropic reported degraded Claude Opus 4 and 4.1 through their status page. We were seeing this affect our model(s) performance, where we activated the relevant warning messages directing users to try other models. This was resolved after an hour on Anthropic's end, and shortly after we saw recovery, returning to our baseline success rate.

Sep 24, 09:16 UTC
Update - Between around 8:16 UTC and 8:51 UTC we saw elevated errors on Claude Opus 4 and Opus 4.1, up to 49% of requests were failing. This has recovered to around 4% of requests failing, we are monitoring recovery.

Sep 24, 09:08 UTC
Investigating - We are currently investigating this issue.

US - Incident with Copilot

2025-09-24T00:26:29Z

Sep 24, 00:26 UTC
Resolved - Between 20:06 UTC September 23 and 04:58 UTC September 24, 2025, the Copilot service experienced degraded availability for Claude Sonnet 4 and 3.7 model requests.

During this period, 0.46% of Claude 4 requests and 7.83% of Claude 3.7 requests failed.

The reduced availability resulted from Copilot disabling routing to an upstream provider that was experiencing issues and reallocating capacity to other providers to manage requests for Claude Sonnet 3.7 and 4.
We are continuing to investigate the source of the issues with this provider and will provide an update as more information becomes available.

Sep 24, 00:26 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 and Claude Sonnet 4 are once again available in Copilot Chat, VS Code and other Copilot products.

We will continue monitoring to ensure stability, but mitigation is complete.

Sep 23, 22:22 UTC
Update - We are experiencing degraded availability for the Claude Sonnet 3.7 and Claude Sonnet 4 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.

Sep 23, 22:22 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Disruption with some GitHub services

2025-09-15T18:28:35Z

Sep 15, 18:28 UTC
Resolved - On September 15th between 17:55 and 18:20 UTC, Copilot experienced degraded availability for all features. This was due a partial deployment of a feature flag to a global rate limiter. The flag triggered behavior that unintentionally rate limited all requests, resulting in 100% of them returning 403 errors. The issue was resolved by reverting the feature flag which resulted in immediate recovery.

The root cause of the incident was from an undetected edge case in our rate limiting logic. The flag was meant to scale down rate limiting for a subset of users, but unintentionally put our rate limiting configuration into an invalid state.

To prevent this from happening again, we have addressed the bug with our rate limiting. We are also adding additional monitors to detect anomalies in our traffic patterns, which will allow us to identify similar issues during future deployments. Furthermore, we are exploring ways to test our rate limit scaling in our internal environment to enhance our pre-production validation process.

Sep 15, 18:21 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-08-27T21:27:59Z

Aug 27, 21:27 UTC
Resolved - On August 27, 2025 between 20:35 and 21:17 UTC, Copilot, Web and REST API traffic experienced degraded performance. Copilot saw an average of 36% of requests fail with a peak failure rate of 77%. Approximately 2% of all non-Copilot Web and REST API traffic requests failed.

This incident occurred after a stale schema cache was used following a database migration. This led to a large number of failed queries. At 21:15 UTC, we applied a fix and by 21:17 UTC, all services had fully recovered.

We have implemented a block for this failure mode as an immediate solution and are actively working to add safeguards to prevent similar issues from occurring in the future.

Aug 27, 21:27 UTC
Update - API Requests and Issues are operating normally.

Aug 27, 21:25 UTC
Update - We've discovered the cause of the service disruption and applied a mitigation.

Aug 27, 20:58 UTC
Update - API Requests and Issues are experiencing degraded performance. We are continuing to investigate.

Aug 27, 20:55 UTC
Update - The team is aware of the root cause of this issue and is working to mitigate the issue quickly.

Aug 27, 20:49 UTC
Update - API Requests is experiencing degraded availability. We are continuing to investigate.

Aug 27, 20:48 UTC
Investigating - We are currently investigating this issue.

US - Some Copilot Models Experiencing Degraded Performance

2025-07-21T07:50:52Z

Jul 21, 07:50 UTC
Resolved - On July 21, 2025, between 07:20 UTC and 08:00 UTC, the Copilot service experienced degraded availability for Claude 4 requests. 2% of Claude 4 requests failed during this time. The issue was caused by an upstream problem affecting our ability to serve requests.
We mitigated by rerouting capacity and monitoring recovery. We are improving detection and mitigation to reduce future impact.

Jul 21, 07:36 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-07-16T08:58:41Z

Jul 16, 08:58 UTC
Resolved - On July 16, 2025, between 05:20 UTC and 08:30 UTC, the Copilot service experienced degraded availability for Claude 3.7 requests. Around 10% of Claude 3.7 requests failed during this time. The issue was caused by an upstream problem affecting our ability to serve requests.
We mitigated by rerouting capacity and monitoring recovery. We are improving detection and mitigation to reduce future impact.

Jul 16, 08:45 UTC
Update - We have seen recovery on our provider's side but have not yet confirmed if the issue is fully resolved. We will update our status in the next 20 minutes as we know more.

Jul 16, 08:21 UTC
Update - We are experiencing degraded availability for the Claude 3.7 Sonnet 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.

Jul 16, 08:16 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-07-03T07:12:02Z

Jul 3, 07:12 UTC
Resolved - On 7/3/2025, between 5:21:17 AM and 7:11:49 AM UTC, customers were prevented from SSO authorizing Personal Access Tokens and SSH keys via the GitHub UI. Approximately 1300 users were impacted.

A code change modified the content type of the response returned by the server, causing a lazily-loaded dropdown to fail to render, prohibiting the user from proceeding to authorize. No authorization systems were impacted during the incident, only the UI component. We mitigated the incident by reverting the code change that introduced the problem.

We are making improvements to our release process and test coverage to catch this class of error earlier in our deployment pipeline. Further, we are improving monitoring to reduce our time to detection and mitigation of issues like this one in the future.

Jul 3, 07:11 UTC
Update - The rollback has been deployed successfully on all environments. Customers should now be able to SSO authorize their Classic Personal Access Tokens and SSH keys on their GitHub organizations.

Jul 3, 06:46 UTC
Update - The root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys has started rolling out. We are continuously monitoring this rollback.

Jul 3, 06:07 UTC
Update - We have identified the root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys.The changes that caused the issue are being rolled back.

Jul 3, 05:45 UTC
Update - We are investigating an issue with SSO authorizing Classic Personal Access Tokens and SSH keys.

Jul 3, 05:39 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-07-02T10:16:27Z

Jul 2, 10:16 UTC
Resolved - On July 2nd, 2025, between approximately 08:40 and 10:16 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Claude Sonnet 4 model, leading to a spike in errors. No other models were impacted.

The issue was mitigated by rebalancing load within our infrastructure. GitHub is working to further improve the resiliency of the service to prevent similar incidents in the future.

Jul 2, 10:16 UTC
Update - We are no longer experiencing degradation—Claude Sonnet 4 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.

Jul 2, 09:57 UTC
Investigating - We are currently investigating this issue.

US - Disruption with Claude 3.7 Sonnet in Copilot Chat

2025-06-30T19:55:38Z

Jun 30, 19:55 UTC
Resolved - On June 30th, 2025, between approximately 18:20 and 19:55 UTC, the Copilot service experienced a degradation of the Claude Sonnet 3.7 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Sonnet 3.7. No other models were impacted.

The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

Jun 30, 19:55 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 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.

Jun 30, 19:14 UTC
Update - We are experiencing degraded availability for the Claude 3.7 Sonnet 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.

Jun 30, 19:13 UTC
Investigating - We are currently investigating this issue.

US - Disruption with the GitHub mobile android application

2025-06-28T01:26:06Z

Jun 28, 01:26 UTC
Resolved - This incident has been resolved.

Jun 27, 12:56 UTC
Investigating - We are currently investigating this issue.

US - Repository Navigation Bar Missing

2025-06-24T12:31:20Z

Jun 24, 12:31 UTC
Resolved - On June 24, 2025 from 09:42 UTC to 12:11 UTC, the Repository UI was degraded for customers using GitHub Enterprise with Data Residency. During this timeframe, the navigational elements on repository pages would not have been visible, impacting roughly 600 users.

The issue was caused by a change that referenced a new resource for this information, which had not yet been configured for the GitHub Enterprise with Data Residency. Additionally, the change had incomplete coverage of the guardrails we employ to prevent these types of exceptions. Due to safe resiliency practices for these elements, the resulting impact was the loss of those elements on the page. A rollback of the impacting change was performed to restore full functionality to these pages.

To prevent future incidents like this, we are investing in additional monitoring for specific errors resulting from these workflows, expanded coverage of end-to-end testing, and alerting when a sharp increase in resilient fallback behavior happens.

Jun 24, 12:26 UTC
Update - We have deployed a mitigation to the affected instances, and telemetry indicates the error is no longer occurring.

Jun 24, 11:44 UTC
Update - A mitigation is in progress of rolling out to the affected instances. We expect customers to see mitigation within the next hour.

Jun 24, 11:34 UTC
Investigating - We are investigating reports of degraded performance for the Repositories UI. We have identified that the navigation bar is missing in GitHub Enterprise Cloud with data residency instances for the repositories related pages and are currently attempting a mitigation.

US - Disruption with some GitHub services

2025-06-18T23:13:52Z

Jun 18, 23:13 UTC
Resolved - On June 18, 2025 between 22:20 UTC and 23:00 UTC the Claude Sonnet 3.7 and Claude Sonnet 4 models for GitHub Copilot Chat experienced degraded performance. During the impact, some users would receive an immediate error when making a request to a Claude model. This was due to upstream errors with one of our model providers, which have since been resolved. We mitigated the impact by disabling the affected provider endpoints to reduce user impact, redirecting Claude Sonnet requests to additional partners.

We are working to update our incident response playbooks for infrastructure provider outages and improve our monitoring and alerting systems to reduce our time to detection and mitigation of issues like this one in the future.

Jun 18, 22:42 UTC
Update - We are experiencing degraded availability for the Claude 4 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. We recommend using Claude 3.7 as an alternative.

Jun 18, 22:40 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Incident with Actions

2025-05-27T13:31:58Z

May 27, 13:31 UTC
Resolved - On May 27, 2025, between 09:31 UTC and 13:31 UTC, some Actions jobs experienced failures uploading to and downloading from the Actions Cache service. During the incident, 6% of all workflow runs couldn’t upload or download cache entries from the service, resulting in a non-blocking warning message in the logs and performance degradation. The disruption was caused by an infrastructure update related to the retirement of a legacy service, which unintentionally impacted Cache service availability. We resolved the incident by reverting the change and have since implemented a permanent fix to prevent recurrence.

We are improving our configuration change processes by introducing additional end-to-end tests to cover the identified gaps, and implementing deployment pipeline improvements to reduce mitigation time for similar issues in the future.

May 27, 13:03 UTC
Update - Mitigation is applied and we’re seeing signs of recovery. We’re monitoring the situation until the mitigation is applied to all affected repositories.

May 27, 12:29 UTC
Update - We are experiencing degradation with the GitHub Actions cache service and are working on applying the appropriate mitigations.

May 27, 12:26 UTC
Investigating - We are investigating reports of degraded performance for Actions

US - Incident with Copilot

2025-05-20T20:02:03Z

May 20, 20:02 UTC
Resolved - On May 20, 2025, between 18:18 UTC and 19:53 UTC, Copilot Code Completions were degraded in the Americas. On average the error rate was 50% of requests to the service in the affected region. This was due to a misconfiguration in load distribution parameters after a scale down operation.

We mitigated the incident by addressing the misconfiguration.

We are working to improve our automated failover and load balancing mechanisms to reduce our time to detection and mitigation of issues like this one in the future.

May 20, 20:02 UTC
Update - The issues with Copilot Code Completions have been resolved.
We will continue monitoring to ensure stability, but mitigation is complete.

May 20, 20:01 UTC
Update - Copilot is operating normally.

May 20, 19:43 UTC
Update - We are experiencing degraded availability for Copilot Code Completions in the America’s.
We are working on resolving the issue.

May 20, 19:37 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Elevated error rates for Claude Sonnet 3.7

2025-05-20T16:08:37Z

May 20, 16:08 UTC
Resolved - On May 20, 2025, between 12:09 PM UTC and 4:07 PM UTC, the GitHub Copilot service experienced degraded availability, specifically for the Claude Sonnet 3.7 model. During this period, the success rate for Claude Sonnet 3.7 requests was highly variable, down to approximately 94% during the most severe spikes. Other models remained available and working as expected throughout the incident.
The issue was caused by capacity constraints in our model processing infrastructure that affected our ability to handle the large volume of Claude Sonnet 3.7 requests.
We mitigated the incident by rebalancing traffic across our infrastructure, adjusting rate limits, and working with our infrastructure teams to resolve the underlying capacity issues. We are working to improve our infrastructure redundancy and implementing more robust monitoring to reduce detection and mitigation time for similar incidents in the future.

May 20, 16:08 UTC
Update - Copilot is operating normally.

May 20, 16:07 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 is once again available in Copilot Chat, VS Code and other Copilot products.

We will continue monitoring to ensure stability, but mitigation is complete.

May 20, 14:59 UTC
Update - We are continuing to work with our model providers on mitigations to increase the success rate of Sonnet 3.7 requests made via Copilot.

May 20, 14:15 UTC
Update - We’re still working with our model providers on mitigations to increase the success rate of Sonnet 3.7 requests made via Copilot.

May 20, 13:33 UTC
Update - We are experiencing degraded availability for the Claude Sonnet 3.7 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.

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