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
Oct 30, 23:29 UTC Resolved - On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated failure rates when dismissing or resolving Dependabot alerts, as well as failures when linking Dependabot update pull requests to Dependabot security alerts. We also observed delays in creating and updating security alerts that extended through November 2, 2026. The unexpected fan-out was caused by a missing job queue throttle after the queues for the fan-out work were migrated as part of system maintenance. We have restored the fan-out throttle and further isolated and throttled these processes to guard against further disruptions. Oct 30, 22:32 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 30, 22:32 UTC Update - We have mitigated impact and are seeing recovery. We are monitoring for full recovery. Oct 30, 21:44 UTC Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more. Oct 30, 21:00 UTC Update - We are investigating elevated errors when viewing some Dependabot alerts. Oct 30, 20:59 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 30, 19:23 UTC Resolved - On October 30, 2026, from 17:50 to 18:32 UTC, Actions, Pages, and Webhooks experienced degraded performance. Actions workflow processing, Pages deployments, and webhook deliveries were delayed, and code search and live updates returned errors. Some Actions queues took additional time to drain after mitigation, and the incident was resolved at 19:23 UTC. The impact was triggered by maintenance on a cloud network gateway connecting an Actions service in the GitHub data center to Redis clusters in the Central US Azure region. The service's Redis client retried aggressively and redialed those connections. That produced a connection storm that saturated the gateway, with about 90% of connection attempts failing. Other services sharing the same network path were degraded as well. We mitigated the incident by removing the affected resources from rotation, which ended the connection storm and allowed the gateway to recover. We have already reduced the number of connection retries in the impacted service and are further improving retry behavior with jittered backoff, shorter connect timeouts, and retry budgets. We are also working with our infrastructure team to make GitHub more resilient to gateway maintenance. Oct 30, 18:32 UTC Monitoring - The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. Oct 30, 18:32 UTC Update - All affected services have recovered following mitigation. We continue to investigate root cause. Oct 30, 18:06 UTC Update - We continue to investigate delays affecting Actions workflows, Pages deployments, and webhook events, along with errors affecting code search and live updates. We have taken mitigation steps. Actions processing and Pages deployments are showing signs of recovery, but impact has not fully resolved. We are monitoring recovery and investigating the underlying cause. Oct 30, 18:00 UTC Update - Pages is experiencing degraded performance. We are continui
Oct 30, 15:02 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 30, 14:49 UTC Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability. Oct 30, 14:48 UTC Update - A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause. Oct 30, 14:45 UTC Update - Issues is operating normally. Oct 30, 14:39 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:36 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:35 UTC Update - We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation. Oct 30, 14:31 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 29, 12:49 UTC Resolved - On October 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded. Live session updates often failed to load, and on average 2.14% of requests to the agent sessions service failed, with a peak of 8.61%. For about 10 minutes around 09:20 UTC, up to 40% of requests to list or create agent sessions failed. Copilot Chat on GitHub.com showed degraded agent session features during this time. The issue occurred when a large increase in task-list requests from a client experiment overloaded the cache that supports the agent sessions service. We mitigated the impact by increasing cache capacity, reducing nonessential load on the cache, and disabling the client experiment. We are moving rate limiting to separate infrastructure, reducing client polling, and improving our alerting so we can detect and respond to this type of overload faster. Oct 29, 12:33 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 29, 11:37 UTC Update - We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. We are actively applying mitigations and monitoring for recovery. Oct 29, 11:01 UTC Update - We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. Oct 29, 10:22 UTC Update - We are experiencing increased failures and latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. Oct 29, 10:19 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 28, 15:28 UTC Resolved - On October 28, 2026, between 13:52 and 15:24 UTC, Copilot users saw errors when using several GPT-family models and the MAI Code 1.1 Flash model. Affected experiences included Copilot Chat in IDEs and on GitHub.com, the Copilot CLI, Copilot Code Review, the Copilot Coding Agent, Code Scanning Autofix, and Code Quality. About 9.73% of requests to the affected models failed, with a peak of about 36.97% at the start of the incident. The errors happened because a credential that we use to authenticate with an upstream model provider became invalid. We mitigated the incident by replacing the credential and redeploying the service. We are strengthening how we manage credentials for upstream providers to prevent this type of failure, returning retryable errors when an upstream provider rejects a request, and improving our monitoring so that we detect and mitigate this type of problem faster in the future. Oct 28, 15:26 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Oct 28, 15:24 UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. Oct 28, 15:15 UTC Update - We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon. Oct 28, 14:55 UTC Update - We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot. Oct 28, 14:33 UTC Update - We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them
Oct 27, 08:00 UTC Resolved - Between 0655 and 0801 UTC on 10/27, customers experienced increased failure rates for API and git requests authenticated with server-to-server tokens for GitHub Apps (excluding Actions tokens). During this window, authenticated git operations mistakenly returned 404 for 1.24% (2.6x) of requests on average and 2.49% (5.3x) at peak. These failures were caused by a scheduled maintenance event where GitHub migrated 7 tables between two MySQL clusters in our IAD and Azure Central US datacenters. One of the affected tables stores installation records for GitHub App server-to-server tokens (excluding Actions). We've successfully completed several of these migrations in recent months without notable customer impact. However, in this case, the migration coincided with a scheduled cleanup job on the installation records table, which deleted approximately 59 million records from 0444-0617 UTC. As a result, the gh-ost tooling used in the migration experienced inter-cluster replication delays (up to 1 hour at peak). At 0655 UTC, we begin transitioning reads of the target tables to the new MySQL cluster, with 100% of reads cutover at 0721 UTC. Customer impact began, but was not detected, throughout the read cutover and persisted until completion of the write cutover at 0801 UTC. We are updating our processes and automation to prevent a repeat of this incident, including disabling overlapping cleanup jobs prior to these migrations and blocking the cutover of reads when replication delays are high.
Oct 26, 18:57 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 26, 18:54 UTC Update - We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC. We mitigated the issue and all services have recovered. Oct 26, 18:50 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 26, 18:48 UTC Investigating - We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests
Oct 24, 00:23 UTC Resolved - Between 23:28 and 00:23 UTC on October 27, 2026, GitHub Copilot experienced degradation affecting Grok 4.6 and Grok 4.7 models. Users encountered elevated error rates when using these models. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation. Oct 24, 00:23 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Oct 23, 23:42 UTC Update - We are experiencing degraded availability for the Grok 4.6 and Grok 4.7 models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot. Oct 23, 23:41 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Oct 23, 18:51 UTC Resolved - We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes. We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users. Oct 23, 18:36 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 23, 17:27 UTC Update - Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. We're continuing to investigate and work to restore normal processing. Oct 23, 16:43 UTC Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more. Oct 23, 16:11 UTC Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more. Oct 23, 15:39 UTC Update - We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available. Oct 23, 15:00 UTC Update - We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available. Oct 23, 14:58 UTC Investigating - We are investi
Oct 23, 08:05 UTC Resolved - On October 23, 2026, between 07:06 UTC and 07:27 UTC, GitHub Actions workflow run results were delayed. Job status, check run updates, and logs in the GitHub UI and API updated with an average delay of about 2 minutes, and some updates were delayed by up to about 7 minutes. During this window, a storage dependency that Actions uses to process workflow logs and artifacts throttled our requests. This slowed result processing, causing updates to queue up. The queue was fully processed by 07:27 UTC, shortly after the throttling stopped. To reduce the risk of recurrence, we have added several storage accounts to increase capacity, and we are working on additional steps to continue to scale. We are also working with our storage provider to understand why the throttling occurred, and improving how result processing handles storage throttling and how quickly we detect it. Oct 23, 07:56 UTC Update - As of 07:27 UTC, Actions results are delivering within normal SLOs again. Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future. Oct 23, 07:53 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Oct 23, 07:31 UTC Update - We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC. Recovery is already being seen but our team is continuing to investigate and monitor performance. Oct 23, 07:29 UTC Investigating - We are investigating reports of degraded performance for Actions
Oct 23, 02:30 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 23, 00:55 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 22, 23:48 UTC Update - GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. We're continuing to work on the remaining delays and monitor recovery. Oct 22, 22:07 UTC Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed. We have seen some recovery, and are working to add more capacity to accelerate the recovery. Oct 22, 20:46 UTC Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed. We've identified interruptions in update processing and are evaluating mitigations to restore normal operation. Oct 22, 19:56 UTC Update - Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing. Oct 22, 19:04 UTC Update - Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring. Oct 22, 18:26 UTC Update - The other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored. Oct 22, 17:43 UTC Update - We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability. Oct 22, 17:41 UTC Update - Actions, Issues, Packages and Pull Requests are operating normally. Oct 22, 17:16 UTC Update - We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search resul
Oct 22, 15:18 UTC Resolved - On October 22, 2026, from 13:05 to 15:20 UTC, our event streaming platform was degraded resulting in elevated job processing latency spikes of 19-35 seconds and elevated job processing times of 4m – this resulted in delayed Actions workflow and step results (up to 13m), notifications (20m) and repository push events (12m). Recovery for repositories began at 14:32, with Actions recovery beginning at 14:59. The issue reoccurred at 16:26 again impacting Actions runs, repo push events, and notifications. Recovery began at 17:16 and completed at 2:07. The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff. Oct 22, 15:18 UTC Update - GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal. Oct 22, 15:17 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Oct 22, 15:06 UTC Update - We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain. Oct 22, 14:35 UTC Update - Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress. Oct 22, 14:19 UTC Update - We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates. Oct 22, 14:18 UTC Investigating - We are investigating reports of degraded performance for Actions
Oct 21, 19: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. Oct 21, 19:22 UTC Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed. Oct 21, 18:52 UTC Update - Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates. Oct 21, 18:18 UTC Update - Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow. Oct 21, 17:09 UTC Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates. Oct 21, 16:59 UTC Update - Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues. Oct 21, 16:57 UTC Update - Actions and Webhooks are operating normally. Oct 21, 16:34 UTC Update - Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more. Oc
Oct 19, 16:56 UTC Resolved - On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. Impact - Workflow status updates, logs, and checks were delayed. - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. Pages deployments and webhooks generated by Actions runs were delayed. An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster. Oct 19, 16:56 UTC Monitoring - Actions, Pages and Webhooks are operating normally. Oct 19, 16:30 UTC Update - We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates,