GitHub Enterprise Cloud - EU Status - Incident History

EU - Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard

Fri, 10 Apr 2026 13:28:21 +0000

Apr 10, 13:28 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.

Apr 10, 13:08 UTC
Update - We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.

Apr 10, 13:07 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

EU - Copilot Coding Agent failing to start some jobs

Thu, 02 Apr 2026 16:30:06 +0000

Apr 2, 16:30 UTC
Resolved - Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.

Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.

This was the same incident declared in https://www.githubstatus.com/incidents/d96l71t3h63k

Apr 2, 16:28 UTC
Update - When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.

We are investigating.

Apr 2, 16:18 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

EU - Incident with Pull Requests: High percentage of 500s

Tue, 31 Mar 2026 21:23:44 +0000

Mar 31, 21:23 UTC
Resolved - On Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures. On average, the error rate was 0.15% and peaked at 0.28% of requests to the service. This was due to a change in garbage collection (GC) settings for a Go-based internal service that provides access to Git repository data. The changes caused more frequent GC activity and elevated CPU consumption on a subset of storage nodes, increasing latency and failure rates for some internal API operations.

We mitigated the incident by reverting the GC changes. To prevent future incidents and improve time to detection and mitigation, we are instrumenting additional metrics and alerting for GC-related behavior, improving our visibility into other signals that could cause degraded impact of this type, and updating our best practices and standards for garbage collection in Go-based services.

Mar 31, 21:16 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Mar 31, 21:12 UTC
Update - We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.

Mar 31, 19:28 UTC
Update - Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.

Mar 31, 18:42 UTC
Update - We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.

Mar 31, 17:16 UTC
Update - We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.

Mar 31, 16:35 UTC
Update - We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.

Mar 31, 16:15 UTC
Update - We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

Mar 31, 15:39 UTC
Update - We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

Mar 31, 15:06 UTC
Update - We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.

Mar 31, 15:05 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests

EU - Teams Github Notifications App is down

Tue, 24 Mar 2026 19:51:17 +0000

Mar 24, 19:51 UTC
Resolved - On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period.

This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration.

We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated.

We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.

Mar 24, 18:51 UTC
Update - We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.

Mar 24, 17:43 UTC
Update - We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.

Mar 24, 17:09 UTC
Update - We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.

Mar 24, 17:00 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

EU - Disruption with Copilot Coding Agent Sessions

Fri, 20 Mar 2026 01:58:39 +0000

Mar 20, 01:58 UTC
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

Mar 20, 01:26 UTC
Update - We are rolling out our mitigation and are seeing recovery.

Mar 20, 01:00 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.

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

EU - Issues with Copilot Coding Agent

Thu, 19 Mar 2026 14:32:56 +0000

Mar 19, 14:32 UTC
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

Mar 19, 14:32 UTC
Monitoring - Copilot is operating normally.

Mar 19, 14:02 UTC
Update - We are investigating reports that Copilot Coding Agent session logs are not available in the UI.

Mar 19, 13:45 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.

Mar 19, 12:32 UTC
Update - We are investigating reports of Copilot coding agent session logs not loading and sessions intermittently not starting. Users are able to see their tasks and create new ones.

Mar 19, 12:00 UTC
Update - We have resolved the underlying credential issue and have verified that users can see and interact with their Copilot Coding Agent tasks.

We are now investigating issues with some Coding Agent tasks completing successfully.

Mar 19, 11:19 UTC
Update - We believe we have identified an underlying credential issue and are working to resolve that across impacted environments.

Mar 19, 10:43 UTC
Update - We are investigating reports of errors when accessing Copilot Coding Agent features. Users may be unable to view or start coding agent tasks through the Agents interface. Our engineers are actively working to restore full functionality.

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

EU - Disruption with some GitHub services

Mon, 16 Mar 2026 15:28:23 +0000

Mar 16, 15:28 UTC
Resolved - On 16 March 2026, between 14:16 UTC and 15:18 UTC, Codespaces users encountered a download failure error message when starting newly created or resumed codespaces. At peak, 96% of the created or resumed codespaces were impacted. Active codespaces with a running VSCode environment were not affected.

The error was a result of an API deployment issue with our VS Code remote experience dependency and was resolved by rolling back that deployment. We are working with our partners to reduce our incident engagement time, improve early detection before they impact our customers, and ensure safe rollout of similar changes in the future.

Mar 16, 15:27 UTC
Update - Errors starting or resuming Codespaces have resolved.

Mar 16, 15:06 UTC
Update - We are investigating reports of users experiencing errors when starting or connecting to Codespaces. Some users may be unable to access their development environments during this time. We are working to identify the root cause and will implement a fix as soon as possible.

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

EU - Disruption with some GitHub services

Thu, 05 Mar 2026 01:30:38 +0000

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.

EU - Some OpenAI models degraded in Copilot

Thu, 05 Mar 2026 01:13:29 +0000

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

EU - Claude Opus 4.6 Fast not appearing for some Copilot users

Tue, 03 Mar 2026 21:11:31 +0000

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

EU - Incident with Copilot and Actions

Tue, 03 Mar 2026 20:09:17 +0000

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, 19:32 UTC
Update - Copilot is operating normally.

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, 18:59 UTC
Investigating - We are investigating reports of degraded performance for Copilot

EU - Incident with Copilot

Thu, 26 Feb 2026 11:06:31 +0000

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

EU - Incident with Copilot Agent Sessions impacting CCA/CCR

Wed, 25 Feb 2026 16:44:50 +0000

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

EU - Incident with Copilot

Mon, 23 Feb 2026 16:19:34 +0000

Feb 23, 16:19 UTC
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:00 UTC
Update - Copilot is operating normally.

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

EU - Incident with Copilot GPT-5.1-Codex

Fri, 20 Feb 2026 11:41:40 +0000

Feb 20, 11:41 UTC
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:19 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, 10:36 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:02 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

EU - Disruption with some GitHub services regarding file upload

Fri, 13 Feb 2026 22:58:43 +0000

Feb 13, 22:58 UTC
Resolved - On February 13, 2026, between 21:46 UTC and 22:58 UTC (72 minutes), the GitHub file upload service was degraded and users uploading from a web browser on GitHub.com were unable to upload files to repositories, create release assets, or upload manifest files. During the incident, successful upload completions dropped by ~85% from baseline levels. This was due to a code change that inadvertently modified browser request behavior and violated CORS (Cross-Origin Resource Sharing) policy requirements, causing upload requests to be blocked before reaching the upload service.

We mitigated the incident by reverting the code change that introduced the issue.

We are working to improve automated testing for browser-side request changes and to add monitoring/automated safeguards for upload flows to reduce our time to detection and mitigation of similar issues in the future.

Feb 13, 22:30 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

EU - Intermittent disruption with Copilot completions and inline suggestions

Thu, 12 Feb 2026 16:50:02 +0000

Feb 12, 16:50 UTC
Resolved - Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded quality and increased latency of up to 500ms for all Next Edit Suggestions requests. The root cause was a newly introduced regression in an upstream service dependency.

The incident was mitigated by failing over Next Edit Suggestions traffic to unaffected regions, which caused the increased latency. Once the regression was identified and rolled back, we restored the impacted capacity. We have improved our quality analysis tooling and are working on more robust quality impact alerting to accelerate detection of these issues in the future.

Feb 12, 15:33 UTC
Update - We are experiencing degraded availability in Western Europe for Copilot completions and suggestions. We are working to resolve the issue.

Feb 12, 14:08 UTC
Update - We are experiencing degraded availability in some regions for Copilot completions and suggestions. We are working to resolve the issue.

Feb 12, 14:06 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

EU - Disruption with some GitHub services

Thu, 12 Feb 2026 11:12:15 +0000

Feb 12, 11:12 UTC
Resolved - From Feb 12, 2026 09:16:00 UTC to Feb 12, 2026 11:01 UTC, users attempting to download repository archives (tar.gz/zip) that include Git LFS objects received errors. Standard repository archives without LFS objects were not affected. On average, the archive download error rate was 0.0042% and peaked at 0.0339% of requests to the service. This was caused by deploying a corrupt configuration bundle, resulting in missing data used for network interface connections by the service.

We mitigated the incident by applying the correct configuration to each site. We have added checks for corruption in this deployment, and will add auto-rollback detection for this service to prevent issues like this in the future.

Feb 12, 11:01 UTC
Update - We have resolved the issue and are seeing full recovery.

Feb 12, 10:39 UTC
Update - We are investigating an issue with downloading repository archives that include Git LFS objects.

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

EU - Copilot Policy Propagation Delays

Tue, 10 Feb 2026 10:01:16 +0000

Feb 10, 10:01 UTC
Resolved - GitHub experienced degraded Copilot policy propagation from enterprise to organizations between February 3 at 21:00 UTC through February 10 at 16:00 UTC. During this period, policy changes could take up to 24 hours to apply. We mitigated the issue on February 10 at 16:00 UTC after rolling back a regression that caused the delays. The propagation queue fully caught up on the delayed items by February 11 at 10:35 UTC, and policy changes now propagate normally.

During this incident, whenever an enterprise updated a Copilot policy (including model policies), there were significant delays before those policy changes reached their child organizations and assigned users. The delay was caused by a large backlog in the background job queue responsible for propagating Copilot policy updates.

Our investigation determined the incident was caused by a code change shipped on February 3 that increased the number of background jobs enqueued per policy update, in order to accommodate upcoming feature work. When new Copilot models launched on February 5th and 7th, triggering policy updates across many enterprises, the higher job volume overwhelmed the shared background worker queue, resulting in prolonged propagation delays. No policy updates were lost; they were queued and processed once the backlog cleared.

We understand these delays disrupted policy management for customers using Copilot at scale and have taken the following immediate steps:

1. Restored the optimized propagation path and put tests in place to avoid a regression.
2. Ensured upcoming features are compatible with this design.
3. Added alerting on queue depth to detect propagation backlogs immediately.

GitHub is critical infrastructure for your work, your teams, and your businesses. We are focused on these mitigations and continued improvements so Copilot policy changes propagate reliably and quickly.

Feb 10, 00:52 UTC
Update - Copilot is operating normally.

Feb 10, 00:26 UTC
Update - We're continuing to address an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them.

This issue is understand and we are working to get the mitigation applied. Next update in one hour.

Feb 9, 22:09 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.

Feb 9, 20:39 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.

Feb 9, 18:49 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Next update in two hours.

Feb 9, 18:06 UTC
Update - We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.

This may prevent newly enabled models from appearing when users try to access them.

Feb 9, 17:23 UTC
Update - We're continuing to investigate a an issue where Copilot policy updates are not propagating correctly for all customers.

This may prevent newly enabled models from appearing when users try to access them.

Feb 9, 16:30 UTC
Update - We’ve identified an issue where Copilot policy updates are not propagating correctly for some customers. This may prevent newly enabled models from appearing when users try to access them.

The team is actively investigating the cause and working on a resolution. We will provide updates as they become available.

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

EU - Incident with Pull Requests

Fri, 06 Feb 2026 18:36:53 +0000

Feb 6, 18:36 UTC
Resolved - On February 6, 2026, between 17:49 UTC and 18:36 UTC, the GitHub Mobile service was degraded, and some users were unable to create pull request review comments on deleted lines (and in some cases, comments on deleted files). This impacted users on the newer comment-positioning flow available in version 1.244.0 of the mobile apps. Telemetry indicated that the failures increased as the Android rollout progressed. This was due to a defect in the new comment-positioning workflow that could result in the server rejecting comment creation for certain deleted-line positions.

We mitigated the incident by halting the Android rollout and implementing interim client-side fallback behavior while a platform fix is in progress. The client-side fallback is scheduled to be published early this week. We are working to (1) add clearer client-side error handling (avoid infinite spinners), (2) improve monitoring/alerting for these failures, and (3) adopt stable diff identifiers for diff-based operations to reduce the likelihood of recurrence.

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:00 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

EU - Incident with Copilot

Tue, 03 Feb 2026 10:56:29 +0000

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

EU - Incident with Actions

Tue, 03 Feb 2026 00:56:05 +0000

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:55 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:42 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

EU - Incident with Actions

Sun, 01 Feb 2026 06:21:31 +0000

Feb 1, 06:21 UTC
Resolved - On February 1, 2026 between 05:05 UTC and 05:40 UTC, customers using the Sweden stamp of GitHub Enterprise Cloud experienced workflow failures and slow job starts on GitHub Actions. During the incident, approximately 2.7% of runs failed, and around 27.5% saw start times averaging 22 minutes. The incident was caused by connection churn in our stream processing system. We've implemented connection churn throttling, improved metrics for faster detection, and are enhancing client connection tooling to prevent recurrence.

Feb 1, 06:20 UTC
Investigating - We are investigating reports of degraded performance for Actions

EU - Copilot Chat - Grok Code Fast 1 Outage

Wed, 21 Jan 2026 12:39:00 +0000

Jan 21, 12:39 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

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

Wed, 14 Jan 2026 10:52:12 +0000

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