Nov 9, 07:43 UTC Investigating - We have observed a repeated increase in 504 errors for anonymous and unauthenticated traffic, including users who are not logged in and release downloads. We are continuing to investigate and apply mitigations. Nov 9, 07:03 UTC Update - The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution. Nov 9, 06:51 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 9, 06:30 UTC Update - We are debugging a spike in anonymous traffic. Some users who are not logged in may see errors on the site. CI jobs and release downloads may fail with a 504 Gateway Timeout status if they make anonymous calls. Nov 9, 05:59 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Nov 8, 12: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. Nov 8, 12:29 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 8, 11:56 UTC Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Nov 8, 11:50 UTC Update - We've identified a problematic component and are working to redeploy it. Nov 8, 11:20 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 8, 11:16 UTC Update - We are continuing to investigate degraded performance primarily for unauthenticated users. Nov 8, 10:36 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Nov 6, 00: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. Nov 6, 00:19 UTC Monitoring - This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report. Nov 6, 00:19 UTC Investigating - Git Operations is operating normally. Nov 6, 00:06 UTC Update - We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC. Nov 6, 00:06 UTC Monitoring - The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability. Nov 5, 23:58 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 5, 23:36 UTC Update - We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC. Nov 5, 23:36 UTC Investigating - We are investigating reports of degraded performance for Actions and Pages
Nov 5, 17:42 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. Nov 5, 17:04 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 5, 16:52 UTC Update - Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation. Nov 5, 16:50 UTC Investigating - We are investigating reports of degraded performance for Actions
Nov 4, 18:16 UTC Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51 Nov 4, 18:07 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 17:53 UTC Update - We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs. Nov 4, 17:40 UTC Investigating - We are investigating reports of degraded availability for Actions
Nov 4, 17:01 UTC Resolved - On November 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were processed after mitigation. This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams. The change depended on feature flags that were not set up as intended, which the service did not handle gracefully. We mitigated the first period by rolling back the configuration change at 16:14 UTC. The code change itself was not reverted by the rollback, so a subsequent deployment reintroduced it. We mitigated the second period at 17:40 UTC by rolling back again, then processed queued events and cleared backlogs. We are taking several steps to prevent a repeat. The routing service will keep its existing behavior when a feature toggle is missing, so a misconfigured flag can no longer pause delivery. We are adding a pre-deploy check that each routing flag exists and is registered under the correct owning service, and we are making flag ownership less error-prone to set. We are also improving alerting so we detect paused event delivery sooner. Nov 4, 16:49 UTC Update - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 16:48 UTC Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Nov 4, 16:45 UTC Update - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Nov 4, 16:34 UTC Update - We have identified an issue with events that might trigger Actio
Nov 4, 11:50 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. Nov 4, 11:43 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 11:30 UTC Update - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 4, 11:17 UTC Update - We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available. Nov 4, 11:11 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 4, 10:38 UTC Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 4, 09:53 UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 4, 09:50 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 4, 09:49 UTC Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
Nov 4, 10:01 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. Nov 4, 10:01 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 09:50 UTC Update - We're continuing to see recovery as rollout continues Nov 4, 09:11 UTC Update - We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery. Nov 4, 08:47 UTC Update - Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations. Nov 4, 08:45 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Nov 3, 22:41 UTC Resolved - On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. This was due to a buildup of excess connections on the hosts that serve Git HTTPS traffic, which saturated their network capacity and caused slow and failed responses for all clients served by those hosts. We mitigated the incident by blocking a client traffic pattern at our load balancers and reloading them, which released the excess connections. The block also prevented some users of one third-party integration from performing Git operations over HTTPS until we removed it on November 4 at 13:26 UTC. We are working to alert on sustained Git HTTPS latency sooner and make load balancer mitigations take effect on existing connections immediately. Nov 3, 22:37 UTC Monitoring - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability. Nov 3, 22:37 UTC Update - We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor. Nov 3, 22:05 UTC Update - Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status. Nov 3, 21:37 UTC Update - We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery. Nov 3, 20:57 UTC Investigating - We are investigating reports of degraded performance for Git Operations
Nov 3, 13:56 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. Nov 3, 13:54 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 3, 13:52 UTC Investigating - API Requests is operating normally. Nov 3, 13:51 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Nov 3, 13:43 UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability. Nov 3, 13:42 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 3, 13:25 UTC Investigating - We are investigating reports of degraded performance for Copilot
Nov 2, 18:24 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. Nov 2, 18:10 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Nov 2, 17:58 UTC Update - We are experiencing degraded availability for the GPT-5.4 Nano model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. Nov 2, 17:46 UTC Update - We are investigating reports of elevated errors on GPT-5.4 Nano Nov 2, 17:46 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers