GitHub Enterprise Cloud US Status - Incident History

US - Incident with Pull Requests

2026-02-06T18:36:52Z

Feb 6, 18:36 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.

Feb 6, 18:36 UTC
Update - Some GitHub Mobile app users may be unable to add review comments on deleted lines in pull requests. We're working on a fix and expect to release it early next week.

Feb 6, 18:04 UTC
Update - Pull Requests is operating normally.

Feb 6, 18:01 UTC
Update - We're currently investigating an issue affecting the Mobile app that can prevent review comments from being posted on certain pull requests when commenting on deleted lines.

Feb 6, 17:49 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests

US - Incident with Copilot

2026-02-03T10:56:28Z

Feb 3, 10:56 UTC
Resolved - On February 3, 2026, between 09:35 UTC and 10:15 UTC, GitHub Copilot experienced elevated error rates, with an average of 4% of requests failing.

This was caused by a capacity imbalance that led to resource exhaustion on backend services. The incident was resolved by infrastructure rebalancing, and we subsequently deployed additional capacity.

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

Feb 3, 10:55 UTC
Update - We are now seeing recovery.

Feb 3, 10:21 UTC
Update - We are investigating elevated 500s across Copilot services.

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

US - Incident with Actions

2026-02-03T00:56:06Z

Feb 3, 00:56 UTC
Resolved - On February 2, 2026, between 18:35 UTC and 22:15 UTC, GitHub Actions hosted runners were unavailable, with service degraded until full recovery at 23:10 UTC for standard runners and at February 3, 2026 00:30 UTC for larger runners. During this time, Actions jobs queued and timed out while waiting to acquire a hosted runner. Other GitHub features that leverage this compute infrastructure were similarly impacted, including Copilot Coding Agent, Copilot Code Review, CodeQL, Dependabot, GitHub Enterprise Importer, and Pages. All regions and runner types were impacted. Self-hosted runners on other providers were not impacted.

This outage was caused by a backend storage access policy change in our underlying compute provider that blocked access to critical VM metadata, causing all VM create, delete, reimage, and other operations to fail. More information is available at https://azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ. This was mitigated by rolling back the policy change, which started at 22:15 UTC. As VMs came back online, our runners worked through the backlog of requests that hadn’t timed out.

We are working with our compute provider to improve our incident response and engagement time, improve early detection before they impact our customers, and ensure safe rollout should similar changes occur in the future. We recognize this was a significant outage to our users that rely on GitHub’s workloads and apologize for the impact this had.

Feb 3, 00:54 UTC
Update - Actions is operating normally.

Feb 2, 23:50 UTC
Update - Based on our telemetry, most customers should see full recovery from failing GitHub Actions jobs on hosted runners.
We are monitoring closely to confirm complete recovery.
Other GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot) should also see recovery.

Feb 2, 23:43 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Feb 2, 23:41 UTC
Update - Copilot is operating normally.

Feb 2, 23:31 UTC
Update - Pages is operating normally.

Feb 2, 22:53 UTC
Update - Our upstream provider has applied a mitigation to address queuing and job failures on hosted runners.
Telemetry shows improvement, and we are monitoring closely for full recovery.

Feb 2, 22:10 UTC
Update - We continue to investigate failures impacting GitHub Actions hosted-runner jobs.
We're waiting on our upstream provider to apply the identified mitigations, and we're preparing to resume job processing as safely as possible.

Feb 2, 21:30 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.

Feb 2, 21:13 UTC
Update - We continue to investigate failures impacting GitHub Actions hosted-runner jobs.
We have identified the root cause and are working with our upstream provider to mitigate.
This is also impacting GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot).

Feb 2, 20:33 UTC
Investigating - We are investigating reports of degraded availability for Actions and Pages

US - Copilot Chat - Grok Code Fast 1 Outage

2026-01-21T12:38:58Z

Jan 21, 12:38 UTC
Resolved - On Jan 21st, 2025, between 11:15 UTC and 13:00 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, more than 90% of the requests to this model failed due to an issue with an upstream provider. No other models were impacted.

The issue was resolved after the upstream provider fixed the problem 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.

Jan 21, 12:09 UTC
Update - We are experiencing degraded availability for the Grok Code Fast 1 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.

Jan 21, 11:33 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Copilot's GPT-5.1 model has degraded performance

2026-01-14T10:52:11Z

Jan 14, 10:52 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.

Jan 14, 10:32 UTC
Update - We are continuing to investigate issues with the GPT-5.1 model. We are also seeing an increase in failures for Copilot Code Reviews.

Jan 14, 09:53 UTC
Update - We are continuing to investigate issues with the GPT-5.1 model with our model provider. Uses of other models are not impacted.

Jan 14, 09:26 UTC
Update - Copilot is experiencing degraded performance when using the GPT-5.1 model. We are investigating the issue.

Jan 14, 09:24 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Disruption with some GitHub services

2026-01-12T10:17:25Z

Jan 12, 10:17 UTC
Resolved - From January 9 13:11 UTC to January 12 10:17 UTC, new Linux Custom Images generated for Larger Hosted Runners were broken and not able to run jobs. Customers who did not generate new Custom Images during this period were not impacted. This issue was caused by a change to improve reliability of the image creation process. Due to a bug, the change triggered an unrelated protection mechanism which determines if setup has already been attempted on the VM and caused the VM to be marked unhealthy. Only Linux images which were generated while the change was enabled were impacted. The issue was mitigated by rolling back the change.

We are improving our testing around Custom Image generation as part of our GA readiness process for the public preview feature.. This includes expanding our canary suite to detect this and similar interactions as part of a controlled rollout in staging prior to any customer impact.

Jan 12, 10:09 UTC
Update - Actions jobs that use custom Linux images are failing to start. We've identified the underlying issue and are working on mitigation.

Jan 12, 10:05 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Jan 12, 10:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

US - Disruption with some GitHub services

2026-01-10T02:33:18Z

Jan 10, 02:33 UTC
Resolved - From January 5, 2026, 00:00 UTC to January 10, 2026, 02:30 UTC, customers using the AI Controls public preview feature experienced delays in viewing Copilot agent session data. Newly created sessions took progressively longer to appear, initially hours, then eventually exceeding 24 hours. Since the page displays only the most recent 24 hours of activity, once processing delays exceeded this threshold, no recent data was visible. Session data remained available in audit logs throughout the incident.

Inefficient database queries in the data processing pipeline caused significant processing latency, creating a multi-day backlog. As the backlog grew, the delay between when sessions occurred and when they appeared on the page increased, eventually exceeding the 24-hour display window.

The issue was resolved on January 10, 2026, 02:30 UTC, after query optimizations and a database index were deployed. We are implementing enhanced monitoring and automated testing to detect inefficient queries before deployment to prevent recurrence.

Jan 10, 02:33 UTC
Update - Our queue has cleared. The last 24 hours of agent session history should now be visible on the AI Controls UI. No data was lost due to this incident.

Jan 9, 23:56 UTC
Update - We estimate the backlogged queue will take 3 hours to process. We will post another update once it is completed, or if anything changes with the recovery process.

Jan 9, 23:44 UTC
Update - We have deployed an additional fix and are beginning to see recovery to the queue preventing AI Sessions from showing in the AI Controls UI. We are working on an estimate for when the queue will be fully processed, and will post another update once we have that information.

Jan 9, 22:41 UTC
Update - We are seeing delays processing the AI Session event queue, which is causing sessions to not be displayed on the AI Controls UI. We have deployed a fix to improve the queue processing and are monitoring for effectiveness. We continue to investigate other mitigation paths.

Jan 9, 21:36 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in AI Controls.

Jan 9, 21:08 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls.

Jan 9, 20:08 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls.

Jan 9, 19:35 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls.

Jan 9, 19:02 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls.

Jan 9, 18:39 UTC
Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls.

Jan 9, 18:08 UTC
Update - Agent Session activity is still observable in audit logs, and this only impacts the AI Controls UI.

Jan 9, 17:57 UTC
Update - We are investigating an incident affecting missing Agent Session data on the AI Settings page on Agent Control Plane.

Jan 9, 17:54 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

US - Some models missing in Copilot

2026-01-07T21:07:09Z

Jan 7, 21:07 UTC
Resolved - On January 7th, 2026, between 17:16 and 19:33 UTC Copilot Pro and Copilot Business users were unable to use certain premium models, including Claude Opus 4.5 and GPT-5.2. This was due to a misconfiguration with Copilot models, inadvertently marking these premium models as inaccessible for users with Copilot Pro and Copilot Business licenses.

We mitigated the incident by reverting the erroneous config change. We are improving our testing processes to reduce the risk of similar incidents in the future, and refining our model availability alerting to improve detection time.

Jan 7, 19:43 UTC
Update - We have implemented a mitigation and confirmed that Copilot Pro and Business accounts now have access to the previously missing models. We will continue monitoring to ensure complete resolution.

Jan 7, 19:29 UTC
Update - We continue to investigate. We'll post another update by 19:50 UTC.

Jan 7, 19:10 UTC
Update - Correction - Copilot Pro and Business users are impacted. Copilot Pro+ and Enterprise users are not impacted.

Jan 7, 19:06 UTC
Update - We continue to investigate this problem and have confirmed only Copilot Business users are impacted. We'll post another update by 19:30 UTC.

Jan 7, 18:44 UTC
Update - We are currently investigating reports of some Copilot Pro premium models including Opus and GPT 5.2 being unavailable in Copilot products. We'll post another update by 19:08 UTC.

Jan 7, 18:33 UTC
Update - We have received reports that some expected models are missing from VSCode and other products using Copilot. We are investigating the cause of this to restore access.

Jan 7, 18:32 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Incident with Copilot

2026-01-06T10:08:06Z

Jan 6, 10:08 UTC
Resolved - On January 6th, 2026, between approximately 8:41 and 10:07 UTC, the Copilot service experienced a degradation of the GPT-5.1-Codex-Max model due to an issue with our upstream provider. During this time, up to 14.17% of requests to GPT-5.1-Codex-Max failed. 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.

Jan 6, 10:07 UTC
Update - The issues with our upstream model provider have been resolved, and GPT-5.1-Codex-Max is once again available.
We will continue monitoring to ensure stability.

Jan 6, 09:03 UTC
Update - We are experiencing degraded availability for the GPT-5.1-Codex-Max 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.

Jan 6, 08:56 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Incident with Copilot Grok Code Fast 1

2025-12-15T15:45:53Z

Dec 15, 15:45 UTC
Resolved - On Dec 15th, 2025, between 14:00 UTC and 15:45 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, 4% of the requests to this model failed due to an issue with our upstream provider. No other models were impacted.

The issue was resolved after the upstream provider fixed the problem 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.

Dec 15, 15:06 UTC
Update - We are continuing to work with our provider on resolving the incident with Grok Code Fast 1. Users can expect some requests to intermittently fail until all issues are resolved.

Dec 15, 14:13 UTC
Update - We are experiencing degraded availability for the Grok Code Fast 1 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.

Dec 15, 14:12 UTC
Investigating - We are investigating reports of degraded performance for Copilot

US - Incident with Git Operations

2025-12-12T20:55:16Z

Dec 12, 20:55 UTC
Resolved - On December 10, 2025 between 18:10 UTC and 20:10 UTC Git Operations for GitHub Data Residency environments experienced periods of failed or delayed git requests to repository, raw, and archive data. On average, the error rate was 4% and peaked at 23% of total requests. This was due to an infrastructure configuration change.

We mitigated the incident by updating our configuration and adding additional capacity to serve the traffic spikes.

We are working to improve our change management in order to reduce our time to detection and mitigation of issues like this one in the future.

Dec 12, 20:55 UTC
Update - The GHEC-DR Sweden region has also seen full recovery. At this time all services are expected to be operating normally.

Dec 12, 20:43 UTC
Update - We have applied the mitigation to all GHEC-DR environments, and are seeing recovery for all regions except Sweden. We're investigating the remaining impact for this region.

Dec 12, 20:40 UTC
Update - Git Operations and Pull Requests are operating normally.

Dec 12, 20:28 UTC
Update - We have identified the issue and are working to mitigate it.

Dec 12, 20:24 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Dec 12, 20:17 UTC
Update - We are currently investigating elevated error rates with Git operations in GHEC-DR environments.

Dec 12, 20:17 UTC
Investigating - We are investigating reports of degraded performance for Git Operations

US - Potential disruption with our Agent Control Plane UI Settings

2025-12-08T21:06:12Z

Dec 8, 21:06 UTC
Resolved - On November 26th, 2025, between approximately 02:24 UTC and December 8th, 2025 at 20:26 UTC, enterprise administrators experienced a disruption when viewing agent session activities in the Enterprise AI Controls page. During this period, users were unable to list agent session activity in the AI Controls view. This did not impact viewing agent session activity in audit logs or directly navigating to individual agent session logs, or otherwise managing AI Agents.

The issue was caused by a misconfiguration in a change deployed on November 25th that unintentionally prevented data from being published to an internal Kafka topic responsible for feeding the AI Controls page with agent session activity information.

The problem was identified and mitigated on December 8th by correcting the configuration issue. GitHub is improving monitoring for data pipeline dependencies and enhancing pre-deployment validation to catch configuration issues before they reach production.

Dec 8, 19:52 UTC
Update - We are investigating an incident affecting missing Agent Session data on the AI Settings page on Agent Control Plane.

Dec 8, 19:51 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

US - Disruption with some GitHub services

2025-11-17T19:08:43Z

Nov 17, 19:08 UTC
Resolved - From Nov 17, 2025 00:00 UTC to Nov 17, 2025 15:00 UTC Dependabot was hitting a rate limit in GitHub Container Registry (GHCR) and was unable to complete about 57% of jobs.

To mitigate the issue we lowered the rate at which Dependabot started jobs and increased the GHCR rate limit.

We’re adding new monitors and alerts and looking into more ways to decrease load on GHCR to help prevent this in the future.

Nov 17, 18:54 UTC
Update - We continue to see recovery and dependabot jobs are currently processing as expected.

Nov 17, 18:18 UTC
Update - We are applying a configuration change and will monitor for recovery.

Nov 17, 17:50 UTC
Update - We are continuing to investigate dependabot failures and a configuration change to mitigate.

Nov 17, 17:15 UTC
Update - We are investigating dependabot job failures affecting approximately 50% of version updates and 25% of security updates.

Nov 17, 16:52 UTC
Investigating - We are currently investigating this issue.

US - Disruption with some GitHub services

2025-11-12T23:04:25Z

Nov 12, 23:04 UTC
Resolved - On November 12, 2025, between 22:10 UTC and 23:04 UTC, Codespaces used internally at GitHub were impacted. There was no impact to external customers. The scope of impact was not clear in the initial steps of incident response, so it was considered public until confirmed otherwise. One improvement from this will be improved clarity of internal versus public impact for similar failures to better inform our status decisions going forward.

Nov 12, 22:51 UTC
Update - We are continuing to investigate connectivity issues with codespaces

Nov 12, 22:26 UTC
Update - We are investing reports of codespaces no longer appearing in the UI or API. Users may experience connectivity issues to the impacted codespaces.

Nov 12, 22:26 UTC
Investigating - We are currently investigating this issue.

US - Experiencing connection issues across Actions, Codespaces, and possibly other services

2025-10-29T23:15:10Z

Oct 29, 23:15 UTC
Resolved - On October 29th, 2025 between 14:07 UTC and 23:15 UTC, multiple GitHub services were degraded due to a broad outage in one of our service providers:

- Users of Codespaces experienced failures connecting to new and existing Codespaces through VSCode Desktop or Web. On average the Codespace connection error rate was 90% and peaked at 100% across all regions throughout the incident period.
- GitHub Actions larger hosted runners experienced degraded performance, with 0.5% of overall workflow runs and 9.8% of larger hosted runner jobs failing or not starting within 5 minutes. These recovered by 20:40 UTC.
- The GitHub Enterprise Importer service was degraded, with some users experiencing migration failures during git push operations and most users experiencing delayed migration processing.
- Initiation of new trials for GitHub Enterprise Cloud with Data Residency were also delayed during this time.
- Copilot Metrics via the API could not access the downloadable link during this time. There were approximately 100 requests during the incident that would have failed the download. Recovery began around 20:25 UTC.

We were able to apply a number of mitigations to reduce impact over the course of the incident, but we did not achieve 100% recovery until our service provider’s incident was resolved.

We are working to reduce critical path dependencies on the service provider and gracefully degrade experiences where possible so that we are more resilient to future dependency outages.

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

us.githubstatus.com was unavailable UTC 2025 Oct 24 02:55 to 03:13

2025-10-24T14:20:55Z

Oct 24, 14:20 UTC
Resolved - On UTC Oct 24 2:55 - 3:15 AM, us.githubstatus.com was unreachable due to service interruption with our status page provider.
During this time, GitHub systems were not experiencing any outages or disruptions.
We are working our vendor to understand how to improve availability of us.githubstatus.com.

US - Disruption with GHEC With Data Residency Signup

2025-10-22T17:35:48Z

Oct 22, 17:35 UTC
Resolved - From 00:00 UTC October 20 2025 to 17:11 UTC October 22 2025, a subset of customers who initiated a trial of GHEC with Data Residency experienced a delay in the provisioning of their GHEC-DR instance. This was caused by timeouts from an inefficient request between internal GitHub services used to create and host SSL certificates for GHEC-DR customer domains. This request has been replaced with a more performant one, and all 77 instances that were impacted have been provisioned successfully. Additionally, we are enhancing the monitoring of GHEC-DR instance provisioning for faster detection.

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.