Jan 14, 00:18 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 13, 23:36 UTC **Update** - We are continuing to investigate increased latency with code search service. Jan 13, 22:53 UTC **Update** - We are investigating reports of increased latency with code search. We will continue to keep users updated on progress towards mitigation. Jan 13, 22:21 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Jan 13, 10:46 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 13, 10:46 UTC **Update** - Copilot is operating normally. Jan 13, 10:44 UTC **Update** - We are seeing recovery in the GPT-4.1 model. We continue to monitor for full recovery. Jan 13, 10:11 UTC **Update** - We are seeing continued recovery across Copilot services but continue to see issues with the GPT-4.1 model that we are investigating. Jan 13, 10:11 UTC **Update** - We are seeing continued recovery across Copilot services but continue to see issues with the GPT-4.1 model that we are investigating. Jan 13, 10:02 UTC **Update** - We have identified what we believe to be a configuration issue that may explain the issue. We have rolled back this change and are starting to see signs of recovery. Jan 13, 09:45 UTC **Update** - We are investigating an issue that is causing failures in all Copilot requests. Jan 13, 09:44 UTC **Update** - Copilot is experiencing degraded availability. We are continuing to investigate. Jan 13, 09:38 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Jan 12, 10:17 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 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:06 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.

Jan 10, 02:33 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 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:07 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:53 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Jan 8, 01:32 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 8, 01:31 UTC **Update** - The issues with our upstream model provider have been resolved, and Grok Code Fast 1 is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete. Jan 8, 00:45 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 8, 00:45 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

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

Jan 6, 17:06 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 6, 16:44 UTC **Update** - We are investigating issues downloading artifacts from Actions workflows. All customers are affected when attempting to download through the web interface. We're actively working on a fix and will post another update by 17:15 UTC. Jan 6, 16:41 UTC **Investigating** - We are investigating reports of degraded performance for Actions

Jan 6, 10:08 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 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

Jan 1, 22:31 UTC **Resolved** - The /features/copilot page has been restored. Jan 1, 21:24 UTC **Update** - Our Copilot feature page (https://github.com/features/copilot) is returning 500s. We are currently investigating. This does not impact the core GitHub application. Jan 1, 21:24 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 23, 10:32 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. Dec 23, 10:32 UTC **Update** - Issues and Pull Requests are operating normally. Dec 23, 10:29 UTC **Update** - We are seeing recovery in search indexing for Issues and Pull Requests. The queue has returned to normal processing times, and we continue to monitor service health. We'll post another update by 11:00 UTC. Dec 23, 09:58 UTC **Update** - We're experiencing delays in search indexing for Issues and Pull Requests. Search results may show data up to three minutes old due to elevated processing times in our indexing pipeline. We're working to restore normal performance. We'll post another update by 10:30 UTC. Dec 23, 09:56 UTC **Investigating** - We are investigating reports of degraded performance for Issues and Pull Requests

Dec 23, 00:17 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. Dec 23, 00:06 UTC **Update** - All services at healthy levels. We're finalizing the change to prevent future degradations from the same source. Dec 22, 23:32 UTC **Update** - We're investigating elevated traffic affecting GitHub services, primarily impacting logged-out users with some increased latency on Issues. We're preparing additional mitigations to prevent further spikes. Dec 22, 22:57 UTC **Update** - We are experiencing elevated traffic affecting some GitHub services, primarily impacting logged-out users. We're actively investigating the full scope and working to restore normal service. We'll post another update by 23:45 UTC. Dec 22, 22:48 UTC **Update** - Issues is experiencing degraded performance. We are continuing to investigate. Dec 22, 22:31 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 18, 19:09 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. Dec 18, 19:09 UTC **Update** - Copilot is operating normally. Dec 18, 19:05 UTC **Update** - We have observed full recovery with updating copilot policy settings, and are validating that that there is no further impact. Dec 18, 18:43 UTC **Update** - Copilot is experiencing degraded performance. We are continuing to investigate. Dec 18, 18:10 UTC **Update** - We have identified the source of this regression and are preparing a fix for deployment. We will update again in one hour. Dec 18, 17:36 UTC **Update** - We are seeing an increase in errors on the User and Org policy settings page when updating policies. The errors are affecting the user copilot policies settings page, org copilot policies settings page when updating a policy. Dec 18, 17:36 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 18, 17:41 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. Dec 18, 17:29 UTC **Update** - We are observing recovery with request from GitHub-hosted Actions runners and will continue to monitor. Dec 18, 16:45 UTC **Update** - Since approximately 8:00 UTC, we have observed intermittent failures on GitHub-hosted actions runners. The failures have been observed both during runner setup, and workflow execution. We are continuing to investigate. Self-hosted runners are not impacted. Dec 18, 16:43 UTC **Investigating** - We are investigating reports of degraded performance for Actions

Dec 18, 16:42 UTC **Resolved** - During an investigation into a unrelated issue, this issue was elevated to public status by mistake, with a title intended for the other incident. We immediately resolved this in order to ensure that our internal investigation was aligned with the correct public status. Dec 18, 16:38 UTC **Update** - Since approximately 8:00 UTC, we have observed intermittent failures on GitHub-hosted actions runners. The failures have been observed both during runner setup, and workflow execution. We are continuing to investigate. Self-hosted runners are not impacted. Dec 18, 16:32 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 16, 12:00 UTC **Resolved** - From 11:50-12:25 UTC, Copilot Coding Agent was unable to process new agent requests. This affected all users creating new jobs during this timeframe, while existing jobs remained unaffected. The cause of this issue was a change to the actions configuration where Copilot Coding Agent runs, which caused the setup of the Actions runner to fail, and the issue was resolved by rolling back this change. As a short term solution, we hope to increase our alerting criteria so that we can be alerted more quickly when an incident occurs, and in the long term we hope to harden our runner configuration to be more resilient against errors.

Dec 15, 18:22 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. Dec 15, 18:21 UTC **Update** - We have seen recovery for Copilot Code Review requests and are investigating long-term availability and scaling strategies Dec 15, 17:43 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 15, 15:45 UTC **Resolved** - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. 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

Dec 11, 20:05 UTC **Resolved** - Between 13:25 UTC and 18:35 UTC on Dec 11th, GitHub experienced an increase in scraper activity on public parts of our website. This scraper activity caused a low priority web request pool to increase and eventually exceed total capacity resulting in users experiencing 500 errors. In particular, this affected Login, Logout, and Signup routes, along with less than 1% requests from within Actions jobs. At the peak of the incident, 7.6% of login requests were impacted, which was the most significant impact of this scraping attack. Our mitigation strategy identified the scraping activity and blocked it. We also increased the pool of web requests that were impacted to have more capacity, and lastly we upgraded key user login routes to higher priority queues. In future, we’re working to more proactively identify this particular scraper activity and have faster mitigation times. Dec 11, 20:05 UTC **Update** - We see signs of full recovery and will post a more in-depth update soon. Dec 11, 19:58 UTC **Update** - We are continuing to monitor and continuing to see signs of recovery. We will update when we are confident that we are in full recovery. Dec 11, 19:04 UTC **Update** - We've applied a mitigation to fix intermittent failures in anonymous requests and downloads from GitHub, including Login, Signup, Logout, and some requests from within Actions jobs. We are seeing improvements in telemetry, but we will continue to monitor for full recovery. Dec 11, 18:47 UTC **Update** - We currently have ~7% of users experiencing errors when attempting to sign up, log in, or log out. We are deploying a change to mitigate these failures. Dec 11, 18:40 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 11, 17:53 UTC **Resolved** - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Dec 11, 17:20 UTC **Update** - Git Operations is operating normally. Dec 11, 17:19 UTC **Update** - We believe that we have narrowed down our affected users to primarily those that are signing up or signing in as well as logged out usage. We are currently continuing to investigate the root cause and are working multiple mitigation angles. Dec 11, 16:41 UTC **Update** - We are experiencing intermittent web request failures across multiple services, including login and authentication. Our teams are actively investigating the cause and working on mitigation. Dec 11, 16:09 UTC **Update** - Codespaces, Copilot, Git Operations, Packages, Pages, Pull Requests and Webhooks are experiencing degraded performance. We are continuing to investigate. Dec 11, 16:01 UTC **Update** - API Requests and Actions are experiencing degraded performance. We are continuing to investigate. Dec 11, 15:47 UTC **Investigating** - We are investigating reports of degraded performance for Issues

Dec 10, 14: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. Dec 10, 14:32 UTC **Update** - We've applied a mitigation to ensure all macOS jobs route to macOS fulfillers and are monitoring for full recovery. Dec 10, 13:34 UTC **Investigating** - We are investigating reports of degraded performance for Actions

Dec 10, 11:05 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. Dec 10, 11:05 UTC **Update** - Actions is operating normally. Dec 10, 11:05 UTC **Update** - We have validated the mitigation and are no longer seeing impact. Dec 10, 10:58 UTC **Update** - We are seeing improvements in telemetry and are monitoring for full recovery. Dec 10, 10:25 UTC **Update** - We've applied a mitigation to fix the issues with queuing and running Actions jobs. We will continue monitoring to confirm whether this resolves the issue. Dec 10, 09:41 UTC **Update** - The team continues to investigate issues with some Actions jobs being queued for a long time. We will continue providing updates on the progress towards mitigation. Dec 10, 09:13 UTC **Update** - We're investigating Actions workflow runs taking longer than expected to start. Dec 10, 09:11 UTC **Investigating** - We are investigating reports of degraded performance for Actions

Dec 8, 22:33 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. Dec 8, 22:10 UTC **Update** - We are beginning to see signs of resolution after applying a mitigation. We expect full resolution within approximately 30 minutes. Dec 8, 22:04 UTC **Update** - We're continuing to investigate and mitigate issues with the GPT 4o model for Copilot completions. Users can currently work around this issue by updating their VS Code settings with "github.copilot.advanced.debug.overrideEngine": "gpt-41-copilot". Dec 8, 21:32 UTC **Update** - We are currently investigating failures with the GPT 4o model for Copilot completions. Dec 8, 21:28 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 8, 21:06 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. 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.

Dec 5, 22:20 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. Dec 5, 21:40 UTC **Update** - We believe we reached a scaling limit and are increasing the amount of resources available to reduce the delays for the team synchronization process. Dec 5, 19:17 UTC **Update** - We're continuing to investigate the delays in the team synchronization and will report back once we have more information. Dec 5, 18:38 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

Dec 3, 22:30 UTC **Resolved** - On December 3, 2025, between 22:21 UTC and 23:44 UTC, the Webhooks service experienced a degradation that delayed writes of webhook delivery records to our database. During this period, many webhook deliveries were not visible in the webhook delivery UI or API for more than an hour after they were sent. As a result, customers were temporarily unable to request redeliveries for those delayed records. The underlying cause was throttling of database writes due to high replication lag. We mitigated the incident by temporarily disabling delivery history for a small number of very high‑volume webhook owners to reduce write pressure and stabilize the service. We are contacting the affected customers directly with more details. We are improving our webhook delivery storage architecture so it can scale with current and future webhook traffic, reducing the likelihood and impact of similar issues.