Duration: 2 days, 12 hours and 59 minutes

Affected Components: Third Party: GitHub → Pull Requests

Sep 1, 15:00:46 GMT+0
Investigating - Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources..

Sep 1, 15:00:22 GMT+0
Investigating - We are investigating reports of degraded performance for Pull Requests.

Sep 1, 16:00:50 GMT+0
Investigating - Time to update pull request diffs have improved to normal thresholds..

Sep 1, 16:01:21 GMT+0
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..

Duration: 3 days, 18 hours and 12 minutes

Affected Components: Third Party: GitHub → Pull Requests, Third Party: GitHub → Actions

Aug 26, 22:57:08 GMT+0
Investigating - We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more..

Aug 27, 00:01:05 GMT+0
Investigating - We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving..

Aug 27, 00:26:05 GMT+0
Monitoring - The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability..

Aug 26, 22:56:31 GMT+0
Investigating - We are investigating reports of degraded performance for Actions and Pull Requests.

Aug 27, 00:25:58 GMT+0
Investigating - We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health..

Aug 27, 00:26:44 GMT+0
Resolved - On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. <br /><br />We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. <br /><br />We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load..

Duration: 7 days, 1 hour and 32 minutes

Affected Components: Third Party: GitHub → Actions

Aug 26, 15:12:21 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Aug 26, 15:11:58 GMT+0
Investigating - We are investigating reports of degraded availability for Actions.

Aug 26, 15:23:10 GMT+0
Investigating - We've identified an issue with a database primary and are failing over to a replica immediately.

Aug 26, 15:48:07 GMT+0
Investigating - primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues.

Aug 26, 18:00:48 GMT+0
Monitoring - All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all new jobs..

Aug 26, 18:01:30 GMT+0
Resolved - On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure, https://www.githubstatus.com/incidents/hcbtzksccj2f, which caused burst amplification of already-high load. Downstream throttles that were later used to recover were set ~10% too high to protect the system. <br /><br />At 15:45 UTC, throttling combined with service restarts recovered the service’s core health. Those throttles were gradually raised between 15:54 and 17:22 to restore full webhook processing for Actions runs. This ramp was deliberately slow to ensure we did not re-overwhelm the system given our original throttling was now known to be incorrectly set. The queue of webhook events was fully burned down at 17:40 UTC. <br /><br />3.7% of larger-runner jobs, along with some scale-set self-hosted jobs, remained stuck in queued or “waiting for runner” state. We deployed a change to force-revoke jobs in this state, and they transitioned to failed at 18:40 UTC, about 50 minutes after incident mitigation. Releasing these jobs also freed hosted concurrency for larger-runner jobs. <br /><br />Customers using concurrency groups saw longer impact due to a separate issue where runners assigned to a subset of jobs disconnected before the force-revoke mitigation was deployed, which prevented runner acquisition from progressing and left jobs in a waiting-for-runner state. This was resolved at 01:00 UTC on August 27. <br /><br />Some runs triggered during the 15:02-15:45 UTC incident window encountered a bug that left them showing as queued even after service recovery. In the backend, these runs had already failed and will automatically move to canceled state 24 hours after creation. As follow-up, we are fixing the root cause of this queued state and improving our ability to bulk-cancel affected runs. <br /><br />Several changes to improve the general scalability of this part of Actions were already complete and deploying to production. Rollout of those changes will be complete within the next 24 hours. Further work to improve scale, resiliency, and more graceful degradation of Actions workflows are in flight. We are also taking a repair item to accelerate clearing of stuck queued or waiting jobs in similar future cases..

Aug 26, 16:14:16 GMT+0
Investigating - We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up..

Aug 26, 16:49:07 GMT+0
Investigating - Pages is operating normally..

Aug 26, 16:50:28 GMT+0
Investigating - We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour..

Aug 26, 17:32:22 GMT+0
Investigating - We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits..

Aug 26, 17:54:33 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Duration: 1 day, 13 hours and 47 minutes

Affected Components: Third Party: GitHub → Actions

Aug 24, 13:56:55 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Aug 24, 14:22:59 GMT+0
Investigating - Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery..

Aug 24, 14:26:11 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Aug 24, 14:34:42 GMT+0
Resolved - On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. <br /><br />To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover..

Duration: 18 days, 23 hours and 43 minutes

Affected Components: Third Party: GitHub → API Requests, Third Party: GitHub → Webhooks, Third Party: GitHub → Pull Requests, Third Party: GitHub → Actions

Aug 17, 14:04:45 GMT+0
Investigating - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will continue to be provided as we investigate..

Aug 17, 13:40:03 GMT+0
Investigating - We are investigating reports of impacted performance for some GitHub services..

Aug 17, 13:41:47 GMT+0
Investigating - API Requests is experiencing degraded performance. We are continuing to investigate..

Aug 17, 13:42:42 GMT+0
Investigating - Actions is experiencing degraded performance. We are continuing to investigate..

Aug 17, 13:44:02 GMT+0
Investigating - Webhooks is experiencing degraded performance. We are continuing to investigate..

Aug 17, 13:45:45 GMT+0
Investigating - We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available.

Aug 17, 15:01:40 GMT+0
Investigating - API Requests is experiencing degraded availability. We are continuing to investigate..

Aug 17, 13:46:37 GMT+0
Investigating - Issues is experiencing degraded performance. We are continuing to investigate..

Aug 17, 13:58:14 GMT+0
Investigating - Pull Requests is experiencing degraded performance. We are continuing to investigate..

Aug 17, 14:24:53 GMT+0
Investigating - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. Investigations are on-going and we will continue to provide updates as we discover more information..

Aug 17, 14:31:25 GMT+0
Investigating - Copilot is experiencing degraded availability. We are continuing to investigate..

Aug 17, 14:45:53 GMT+0
Investigating - Pull Requests is experiencing degraded availability. We are continuing to investigate..

Aug 17, 21:15:46 GMT+0
Resolved - On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. SAML/OIDC authentication, SCIM, and Team Sync were also affected, as well as Actions workflows in GHEC with Data Residency that depend on public workflow step definitions hosted on GitHub.com. Most services recovered by 16:36 UTC as our Central US datacenter recovered; Actions was degraded until approximately 18:03 UTC; and Copilot Token Service fully recovered by 21:02. <br /><br />Some of the failing traffic was moved from Central US to Northern Virginia where it was served successfully until the network failure in Central US was debugged and resolved. Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service. <br /><br />The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery. <br /><br />The retry storm in Northern VA was fixed by 1) temporarily reducing gateway retry logic with a PR and 2) blocking inbound Copilot Token Service token requests at the load balancers with a 403, and then gradually ramping back up traffic per-site to allow callers to succeed. <br /><br />Residual Copilot authentication failures continued because client retry behavior amplified load: a failed token operation could generate many extra requests and enter a retry loop. Copilot Token Service traffic increased from a normal 7–9K RPS to 70–100K RPS. Reducing gateway authentication retries and blocking retry-triggering responses stabilized Copilot Token Service and completed recovery. <br /><br />Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints. <br /><br />To prevent recurrence, our follow-up actions include: <br /><br />- Correcting autoscaling policies to account for service-mesh sidecar concurrency and capacity. <br /><br />- Auditing Istio request, concurrency, and scaling limits across affected services. <br /><br />- Reviewing retry limits and backoff behavior across gateways and clients. <br /><br />- Addressing the VS Code retry behavior that amplified Copilot token traffic. <br /><br />- Improving load-balancer capacity monitoring and regional failover safeguards..

Aug 17, 14:49:24 GMT+0
Investigating - Issues is experiencing degraded availability. We are continuing to investigate..

Aug 17, 14:54:14 GMT+0
Investigating - Pull Requests is experiencing degraded availability. We are continuing to investigate..

Aug 17, 14:58:09 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Aug 17, 14:58:12 GMT+0
Investigating - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations based on our investigation thus far and are monitoring for improvement..

Aug 17, 14:58:17 GMT+0
Investigating - Webhooks is experiencing degraded availability. We are continuing to investigate..

Aug 17, 15:10:00 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Aug 17, 15:21:36 GMT+0
Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate..

Aug 17, 15:40:44 GMT+0
Investigating - Webhooks is experiencing degraded performance. We are continuing to investigate..

Aug 17, 15:42:25 GMT+0
Investigating - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations and will post updates as we progress..

Aug 17, 16:16:13 GMT+0
Investigating - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are still working to identify the root cause and will continue to post updates as we learn more and perform mitigation..

Aug 17, 16:36:25 GMT+0
Investigating - We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service, with error rates still remaining slightly elevated. We will post further updates as recovery continues..

Aug 17, 16:59:38 GMT+0
Investigating - The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability..

Aug 17, 17:34:22 GMT+0
Investigating - We identified the problematic component and have taken corrective actions, but we are seeing residual impact across numerous services. We are continuing to apply additional mitigations and investigate the remaining impact..

Aug 17, 17:36:29 GMT+0
Investigating - Issues is experiencing degraded performance. We are continuing to investigate..

Aug 17, 18:11:30 GMT+0
Investigating - We identified the problematic component and have taken corrective actions, but we are seeing residual impact in the form of sporadic authentication failures. We are continuing to apply additional mitigations and investigate the remaining impact..

Aug 17, 18:23:47 GMT+0
Investigating - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability..

Aug 17, 18:48:19 GMT+0
Investigating - API Requests is experiencing degraded availability. We are continuing to investigate..

Aug 17, 19:01:45 GMT+0
Investigating - API Requests is operating normally..

Aug 17, 20:22:28 GMT+0
Investigating - Issues is operating normally..

Aug 17, 19:13:20 GMT+0
Investigating - We are continuing to investigate sporadic authentication failures. We have partially disabled authentication token retries and have seen improvement, and we are monitoring impact before fully applying this mitigation..

Aug 17, 20:08:40 GMT+0
Investigating - We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected..

Aug 17, 20:45:28 GMT+0
Investigating - We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications. We expect full recovery within the next 30 minutes. Copilot usage via the GitHub CLI and GitHub App are unaffected..

Aug 17, 17:30:49 GMT+0
Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate..

Duration: 2 days, 2 hours and 54 minutes

Affected Components: Third Party: GitHub → Webhooks, Third Party: GitHub → Pull Requests

Aug 13, 14:45:40 GMT+0
Investigating - We are investigating reports of degraded performance for Webhooks.

Aug 13, 14:46:11 GMT+0
Investigating - Pull Requests is experiencing degraded performance. We are continuing to investigate..

Aug 13, 14:46:23 GMT+0
Investigating - Issues is experiencing degraded performance. We are continuing to investigate..

Aug 13, 14:46:52 GMT+0
Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate..

Aug 13, 14:56:45 GMT+0
Investigating - Packages is experiencing degraded performance. We are continuing to investigate..

Aug 13, 14:58:49 GMT+0
Investigating - We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence..

Aug 13, 15:33:02 GMT+0
Monitoring - The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability..

Aug 13, 15:33:54 GMT+0
Monitoring - We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated..

Aug 13, 15:36:34 GMT+0
Resolved - Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. <br /><br />Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. <br /><br />To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future..

Duration: 1 day and 1 hour

Affected Components: Third Party: GitHub → Pull Requests

Aug 12, 16:16:18 GMT+0
Investigating - We are investigating reports of degraded performance for Issues and Pull Requests.

Aug 12, 16:24:30 GMT+0
Investigating - We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information..

Aug 12, 16:35:40 GMT+0
Monitoring - The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability..

Aug 12, 16:38:38 GMT+0
Monitoring - We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution..

Aug 12, 16:41:18 GMT+0
Resolved - Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors..

Duration: 13 days, 4 hours and 16 minutes

Affected Components: Third Party: GitHub → API Requests

Aug 11, 14:50:40 GMT+0
Investigating - We are investigating reports of degraded performance for API Requests.

Aug 11, 15:28:44 GMT+0
Investigating - We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information.

Aug 11, 16:49:24 GMT+0
Investigating - We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident..

Aug 11, 16:49:34 GMT+0
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability..

Aug 11, 20:06:50 GMT+0
Monitoring - We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident..

Aug 11, 20:06:56 GMT+0
Resolved - On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. <br /><br />This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck. <br /><br />We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future..

Duration: 26 days, 17 hours and 55 minutes

Affected Components: Third Party: GitHub → Actions

Aug 7, 00:01:26 GMT+0
Investigating - System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly..

Aug 7, 00:05:05 GMT+0
Investigating - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability..

Aug 7, 00:06:24 GMT+0
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability..

Aug 7, 00:59:01 GMT+0
Monitoring - We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses..

Aug 7, 02:04:44 GMT+0
Resolved - On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes. <br /><br />The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services. <br /><br />These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events. <br /><br />As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work. <br /><br />This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation. <br /><br />Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases. <br /><br />Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043. <br /><br />To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions..

Aug 7, 02:03:41 GMT+0
Monitoring - During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.<br /><br />The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.<br /><br />Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable..

Aug 6, 17:02:43 GMT+0
Investigating - We are continuing to work on the issue affecting GitHub Actions. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures. <br /><br />Our engineers have applied several mitigations and are rolling out a further fix now..

Aug 6, 21:30:42 GMT+0
Investigating - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs.<br /><br />We identified runners being assigned jobs that are no longer valid and are deploying a change to address this issue. Both GitHub-hosted and self-hosted runners are affected.<br /><br />Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts..

Aug 6, 17:40:22 GMT+0
Investigating - We are continuing to work on an issue affecting multiple GitHub services.<br /><br />Workflow runs are failing or delayed in starting, and some queued jobs may time out. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected. <br /><br />Webhook deliveries may be delayed. <br /><br />Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now..

Aug 6, 20:34:17 GMT+0
Investigating - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs queued, approximately 65% are succeeding, improved from a low of 30 to 40% earlier in this incident.<br /><br />We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.<br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected..

Aug 7, 00:01:15 GMT+0
Investigating - <br />System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly..

Aug 6, 18:11:41 GMT+0
Investigating - We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected. <br /><br />Webhook deliveries may be delayed.<br /><br />Engineers have applied further mitigations and are continuing to work towards full recovery..

Aug 6, 18:46:37 GMT+0
Investigating - We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. <br /><br />Recovery is taking longer than we expected, and engineers remain actively engaged..

Aug 6, 22:18:09 GMT+0
Investigating - We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased significantly and are now at 97%. Standard and larger runners are now draining queued work. A change is also in progress to mitigate issues with existing self-hosted runners that are not picking up jobs.<br /><br />Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.<br /><br />GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.<br /><br />We are continuing to monitor recovery and will provide another update as conditions improve..

Aug 6, 19:43:21 GMT+0
Investigating - We are continuing to work on an issue affecting GitHub Actions. <br /><br />Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. Customers using self-hosted runners may see errors or rate limiting when runners register.  <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. <br /><br />Our engineers remain actively engaged..

Aug 6, 23:13:30 GMT+0
Investigating - We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.<br /><br />We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.<br /><br />GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.<br /><br />We continue to monitor recovery across all affected services and will provide another update as conditions improve..

Aug 6, 15:22:49 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Aug 6, 16:27:01 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Aug 6, 15:41:10 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Aug 6, 15:45:14 GMT+0
Investigating - We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors. <br /><br />Some customers may also see unexpected rate limiting in their workflows. <br /><br />Engineers have identified the source of the disruption and are actively working on a mitigation.

Aug 6, 15:53:22 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Aug 6, 16:19:30 GMT+0
Investigating - Pages is operating normally..

Aug 6, 16:27:47 GMT+0
Investigating - We are continuing to work on the issue affecting GitHub Actions. <br /><br />Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors. <br /><br />Customers running migrations with GitHub Enterprise Importer may also see failures. <br /><br />Engineers are actively working towards full recovery..

Aug 6, 16:33:31 GMT+0
Investigating - Actions and Pages are experiencing degraded availability. We are continuing to investigate..

Duration: 1 day, 10 hours and 29 minutes

Affected Components: Third Party: GitHub → Actions

Jul 29, 15:26:24 GMT+0
Investigating - We are investigating reports of degraded availability for Actions.

Jul 29, 15:34:07 GMT+0
Investigating - We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure..

Jul 29, 15:40:35 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 29, 16:00:54 GMT+0
Resolved - On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future..

Duration: 15 hours and 51 minutes

Affected Components: Third Party: GitHub → API Requests

Jul 27, 03:53:19 GMT+0
Investigating - We are investigating reports of degraded performance for API Requests.

Jul 27, 04:09:10 GMT+0
Resolved - On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or altered. Other GitHub services were not affected.<br /><br />The errors were traced to a single group of servers handling a share of GraphQL API traffic. Application processes on that group intermittently closed connections before completing responses. Impact ended at 03:52 UTC on July 27 when those processes were replaced, and we resolved the incident at 04:09 UTC on July 27 after confirming error rates had returned to normal.<br /><br />We are still investigating why those processes closed connections, and that work is being carried out by the team that owns the underlying compute platform. In the meantime we are adding detection and automated mitigation for when a single group of servers behaves differently from its peers..

Jul 27, 04:09:01 GMT+0
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability..

Duration: 1 day, 17 hours and 30 minutes

Affected Components: Third Party: GitHub → Actions

Jul 25, 12:34:26 GMT+0
Investigating - We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality..

Jul 25, 12:58:32 GMT+0
Investigating - We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure..

Jul 25, 12:59:58 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 25, 13:12:41 GMT+0
Monitoring - We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried..

Jul 25, 13:13:21 GMT+0
Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8.

Jul 25, 12:31:51 GMT+0
Investigating - We are investigating reports of degraded availability for Actions.

Duration: 1 day, 1 hour and 53 minutes

Affected Components: Third Party: GitHub → Actions

Jul 25, 08:59:37 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Jul 25, 09:13:09 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 25, 09:20:23 GMT+0
Monitoring - We identified an issue causing delays in GitHub Actions run starts. Some users may have experienced longer than expected wait times when triggering workflow runs. We have applied mitigations and have recovered. Our team continues to monitor and investigate the root cause..

Jul 25, 09:25:30 GMT+0
Resolved - On July 25, 2026, GitHub Actions experienced two related periods of degradation that caused some workflow runs to be delayed by more than 5 minutes or end with infrastructure failures. <br /><br />First period (08:45 – 09:13 UTC): During planned maintenance on a critical-path Redis cluster for Actions, one participating region was left in a degraded state. Separately, an independent capacity operation temporarily removed another region from the cluster and redirected its traffic to the degraded region. This created cross-region inconsistencies in job-assignment state, causing workflow runs to be delayed, exhaust retries, or fail outright. At peak, about 7% of runs were delayed by more than 5 minutes, and 25% of runs failed with an infrastructure error during the course of the incident. We mitigated the incident at 09:13 UTC by returning traffic to its normal distribution. <br /><br />Second period (12:08 – 12:48 UTC): As part of mitigating the first incident, traffic was returned to the regional instance that was still undergoing its capacity increase. Multiple Redis nodes in the scaling region experienced failures, increasing traffic to healthy nodes and causing connection limits to be reached on many nodes. At peak, 30% of runs were delayed by more than 5 minutes, and 60% of runs failed with an infrastructure error during the course of the incident. We mitigated the incident at 12:48 UTC by redirecting workflow traffic away from the scaling region. <br /><br />We are adding stronger regional health and capacity checks before maintenance and requiring a stable observation period before restoring traffic. We are also improving automated connection resiliency, and partnering with our platform dependency to automatically detect and remediate unhealthy cluster members and shard imbalance. More generally, we already had work underway to improve the resiliency and scale of this piece of Actions infrastructure..

Duration: 1 day, 21 hours and 42 minutes

Affected Components: Third Party: GitHub → Pull Requests

Jul 24, 19:37:28 GMT+0
Investigating - We are investigating reports of degraded performance for Pull Requests.

Jul 24, 19:40:45 GMT+0
Investigating - We are investigating errors creating pull requests.

Jul 24, 19:43:40 GMT+0
Investigating - Pull Requests is experiencing degraded availability. We are continuing to investigate..

Jul 24, 19:59:57 GMT+0
Investigating - We have applied a mitigation and are monitoring for recovery.

Jul 24, 20:02:39 GMT+0
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability..

Jul 24, 20:23:10 GMT+0
Resolved - Between July 24, 19:17 UTC and July 24, 20:02 UTC, users were unable to create pull requests due to a database schema change. In total, 113,930 pull request creation attempts were impacted across 50,904 users, with an average error rate of 1.75% and a maximum error rate of 2.25% for all requests to Pull Requests service. Existing pull requests and other GitHub functionality were not affected. The issue was resolved by reverting the change to the affected database, upon which pull request creation immediately resumed.<br /><br />The root cause was related to a backfill workflow into the Vitess keyspace hosting Pull Request data. The backfill Vitess command encountered errors and increased VReplication lag, and the workflow was canceled at 19:17 UTC. The cancellation executed a misunderstood Vitess codepath that dropped the backing table to the target keyspace, leaving a non-existent reference that resulted in errors creating Pull Requests. The mitigation was executing a command to drop the vschema reference to the dropped table, allowing Pull Request creation to resume.<br /><br />We are adding stronger pre-flight validation to our tooling to prevent similar issues and expanding lower-environment support to provide better test coverage end-to-end before promoting them to production. We're also fixing our backfill migration tooling to protect from this specific codepath..

Duration: 3 days, 7 hours and 19 minutes

Affected Components: Third Party: GitHub → API Requests, Third Party: GitHub → Pull Requests, Third Party: GitHub → Actions

Jul 24, 16:17:31 GMT+0
Investigating - We are investigating reports of degraded performance for API Requests and Issues.

Jul 24, 16:19:39 GMT+0
Investigating - Actions is experiencing degraded performance. We are continuing to investigate..

Jul 24, 16:22:37 GMT+0
Investigating - We are investigating timeouts to some GitHub services.

Jul 24, 16:28:37 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jul 24, 16:20:10 GMT+0
Investigating - Pull Requests is experiencing degraded performance. We are continuing to investigate..

Jul 24, 16:26:47 GMT+0
Investigating - Copilot is experiencing degraded performance. We are continuing to investigate..

Jul 24, 16:27:51 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Jul 24, 16:40:27 GMT+0
Investigating - We have applied a mitigation and are monitoring for recovery.

Jul 24, 16:41:59 GMT+0
Investigating - Actions is experiencing degraded performance. We are continuing to investigate..

Jul 24, 17:16:44 GMT+0
Investigating - The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability..

Jul 24, 17:24:27 GMT+0
Investigating - We are seeing recovery across all services.

Jul 24, 17:36:50 GMT+0
Resolved - On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ. <br /><br />Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors: <br /><br />- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts. <br />- 27% of GitHub issues interactions saw slow requests or timeouts. <br />- 4% of GitHub Copilot requests experienced errors, though most automatically retry. <br />- 4% of git push operations saw impacts during the affected window. <br />- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases. <br /><br />We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36. <br /><br />This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss..

Duration: 4 days, 9 hours and 20 minutes

Affected Components: Third Party: GitHub → Webhooks, Third Party: GitHub → Pull Requests, Third Party: GitHub → Actions

Jul 23, 07:53:59 GMT+0
Investigating - We are investigating reports of degraded availability for Actions, Issues and Webhooks.

Jul 23, 08:25:16 GMT+0
Investigating - Pull Requests is experiencing degraded performance. We are continuing to investigate..

Jul 23, 08:34:23 GMT+0
Investigating - We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted..

Jul 23, 09:18:37 GMT+0
Investigating - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability..

Jul 23, 09:19:49 GMT+0
Investigating - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 23, 09:22:21 GMT+0
Investigating - We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services..

Jul 23, 09:27:35 GMT+0
Investigating - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability..

Jul 23, 09:35:17 GMT+0
Investigating - Webhooks is operating normally..

Jul 23, 09:39:11 GMT+0
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability..

Jul 23, 09:39:19 GMT+0
Resolved - On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident. <br /><br />The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered. <br /><br />To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot..

Duration: 3 days, 13 hours and 43 minutes

Affected Components: Third Party: GitHub → Actions

Jul 22, 20:43:43 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Jul 22, 20:47:02 GMT+0
Investigating - Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation..

Jul 22, 22:01:51 GMT+0
Investigating - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 22, 22:01:57 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 22, 22:09:26 GMT+0
Resolved - On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start.<br /><br />At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents..

Duration: 12 days, 21 hours and 59 minutes

Affected Components: Third Party: GitHub → API Requests, Third Party: GitHub → Actions

Jul 20, 00:49:33 GMT+0
Investigating - Actions and Pages are experiencing degraded performance. We are continuing to investigate..

Jul 20, 00:52:40 GMT+0
Investigating - Issues is experiencing degraded performance. We are continuing to investigate..

Jul 19, 23:34:03 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Jul 19, 23:37:51 GMT+0
Investigating - We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can..

Jul 19, 23:57:14 GMT+0
Investigating - We have identified the cause of failures in GitHub Actions and are working to restore service..

Jul 20, 00:07:41 GMT+0
Investigating - API Requests is experiencing degraded availability. We are continuing to investigate..

Jul 20, 00:20:23 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jul 20, 00:48:31 GMT+0
Investigating - Actions is experiencing degraded performance. We are continuing to investigate..

Jul 20, 03:27:10 GMT+0
Investigating - We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery..

Jul 20, 03:34:48 GMT+0
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..

Jul 20, 01:11:39 GMT+0
Investigating - We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.<br /><br />A separate incident was opened before we understood they were related. We will continue to post updates on this incident..

Jul 20, 01:37:10 GMT+0
Investigating - Pages is operating normally..

Jul 20, 02:20:04 GMT+0
Investigating - Issues is operating normally..

Jul 20, 02:23:53 GMT+0
Investigating - API Requests is experiencing degraded performance. We are continuing to investigate..

Jul 20, 04:43:50 GMT+0
Monitoring - Actions has fully recovered, and we will continue to monitor the platform to ensure stability..

Jul 20, 03:03:45 GMT+0
Investigating - API Requests is operating normally..

Jul 20, 02:43:43 GMT+0
Investigating - Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners..

Jul 20, 04:44:03 GMT+0
Resolved - Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates. <br /><br />The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.<br /><br />To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs..

Duration: 3 days, 10 hours and 54 minutes

Affected Components: Third Party: GitHub → API Requests

Jul 17, 00:00:47 GMT+0
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability..

Jul 16, 22:58:03 GMT+0
Investigating - We are aware of degraded REST API availability and are investigating.

Jul 17, 00:14:08 GMT+0
Resolved - From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%. <br /><br />We identified the issue as an infrastructure change that wrongly marked the majority of API backends in a single region as unhealthy. As a result, requests routed to those backends failed before reaching the application layer. <br /><br />To prevent this from happening again, we're improving our systems to catch this kind of invalid configuration before it reaches production. We'll also audit the related systems to make them more resilient to future changes, and we're increasing our monitoring sensitivity so we're alerted to problems like this sooner..

Jul 16, 22:51:13 GMT+0
Investigating - We are investigating reports of impacted performance for some GitHub services..

Jul 16, 22:58:23 GMT+0
Investigating - API Requests is experiencing degraded performance. We are continuing to investigate..

Jul 16, 23:29:04 GMT+0
Investigating - We are continuing to investigate an issue causing approximately 35% of REST API requests to fail.  Based on our current understanding, requests are not consistently reaching the application layer, resulting in failed requests returning HTML responses instead of the expected API response format. We are actively investigating the issue and will provide another update as soon as more information is available..

Jul 17, 00:14:04 GMT+0
Monitoring - As of 23:46 UTC, the REST API service is reachable and responding to requests normally..

Duration: 23 hours and 28 minutes

Affected Components: Third Party: GitHub → Webhooks

Jul 14, 17:38:28 GMT+0
Investigating - We are investigating reports of degraded performance for Webhooks.

Jul 14, 17:55:50 GMT+0
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability..

Jul 14, 17:55:45 GMT+0
Investigating - Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable.<br /><br />Impact resolved automatically once the deployment completed..

Jul 14, 18:01:57 GMT+0
Resolved - On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery. The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in progress, affected records were silently skipped rather than persisted, with no automatic retry. The impact ended as soon as the rollout was completed. About 2.4M delivery records were skipped (approximately 4% of the 20-minute impact window, 0.04% of a typical 24-hour period). Importantly, 95% of these skipped deliveries reached customer endpoints successfully, only the record of the delivery is missing. Of the ~5% that failed to reach customer endpoints, only ~1.4% (5,463) map to webhooks that retried their deliveries in the past 28 days. To prevent recurrence, we are improving our automated detection of unsafe schema changes and tightening rollout coordination for changes that span multiple components in the pipeline..

Duration: 21 hours and 34 minutes

Affected Components: Third Party: GitHub → Actions

Jul 13, 13:32:22 GMT+0
Investigating - We are investigating reports of degraded availability for Actions.

Jul 13, 13:32:44 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Jul 13, 13:39:27 GMT+0
Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability..

Jul 13, 13:53:57 GMT+0
Resolved - On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes. <br /><br />The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained. <br /><br />To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied..

Duration: 23 days, 5 hours and 52 minutes

Affected Components: Third Party: GitHub → Actions

Jul 9, 13:16:36 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jul 9, 13:39:48 GMT+0
Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability..

Jul 9, 13:41:26 GMT+0
Monitoring - Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated.<br /><br />We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure..

Jul 9, 04:34:25 GMT+0
Investigating - We are investigating reports of degraded performance for Actions.

Jul 9, 12:46:13 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jul 9, 10:07:04 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jul 9, 12:36:33 GMT+0
Investigating - Pages is experiencing degraded performance. We are continuing to investigate..

Jul 9, 06:01:43 GMT+0
Investigating - We are continuing to work on a mitigation..

Jul 9, 10:15:25 GMT+0
Investigating - Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start..

Jul 9, 04:51:43 GMT+0
Investigating - Approximately 5% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation..

Jul 9, 12:01:59 GMT+0
Investigating - Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.<br />This has caused some customers to exceed their hosted compute concurrency and experience increased impact.<br /><br />We are continuing to working on infrastructure mitigations. <br /><br />Next update in one hour..

Jul 9, 12:54:24 GMT+0
Investigating - We're seeing Actions and Pages recovery. <br /><br />For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing.<br /><br />GitHub pages builds were also failing during that period, but Pages are still accessible.<br /><br />We are continuing to monitor for full recovery..

Jul 9, 13:17:04 GMT+0
Investigating - We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog.<br /><br />Customers may see a small rate of  API and job failures as the system is recovering.<br /><br />Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery.<br /><br />Pages were accessible throughout the incident..

Jul 9, 13:52:16 GMT+0
Resolved - On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start.<br /><br />At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents..

Duration: 5 days, 2 hours and 37 minutes

Affected Components: Third Party: GitHub → Actions

Jul 7, 15:06:56 GMT+0
Investigating - Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful.<br /><br />We continue to investigate the source of these errors..

Jul 7, 14:14:40 GMT+0
Investigating - We are investigating reports of degraded performance for Actions and Codespaces.

Jul 7, 16:00:01 GMT+0
Investigating - We have rolled out the mitigation and are seeing recovery..

Jul 7, 14:32:57 GMT+0
Investigating - Codespaces is experiencing degraded availability. We are continuing to investigate..

Jul 7, 14:14:52 GMT+0
Investigating - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.<br /><br />Actions runs in progress are continuing successfully..

Jul 7, 14:47:06 GMT+0
Investigating - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time.  Retries may be successful.<br /><br />Actions runs and codespaces  in progress are continuing successfully.<br /><br />We are continuing to investigate the source of these errors..

Jul 7, 15:50:02 GMT+0
Investigating - Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation..

Jul 7, 16:02:02 GMT+0
Monitoring - The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability..

Jul 7, 16:17:16 GMT+0
Resolved - On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors.<br /><br />We mitigated the incident by rolling back the change, after which the affected services recovered.<br /><br />We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future..

Duration: 1 day, 13 hours and 32 minutes

Affected Components: Third Party: GitHub → Webhooks, Third Party: GitHub → Pull Requests, Third Party: GitHub → Actions

Jun 25, 17:50:19 GMT+0
Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks.

Jun 25, 18:27:23 GMT+0
Monitoring - We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered..

Jun 25, 17:58:46 GMT+0
Investigating - Issues is experiencing degraded performance. We are continuing to investigate..

Jun 25, 17:53:09 GMT+0
Investigating - Actions is experiencing degraded availability. We are continuing to investigate..

Jun 25, 18:07:44 GMT+0
Monitoring - The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability..

Jun 25, 18:27:52 GMT+0
Resolved - On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. <br /><br />The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07..

Duration: 8 hours and 20 minutes

Affected Components: GitHub Runners

Jun 24, 15:32:02 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jun 24, 13:38:00 GMT+0
Identified - We've identified an issue with Github API rate limiting that causes jobs to be delayed up to 25mins for some customers. We are continuing to work on a fix for this incident..

Jun 24, 18:07:48 GMT+0
Resolved - This incident has been resolved. Zero recurrence in the last 2 hours. .

Jun 24, 18:51:33 GMT+0
Investigating - We have observed a reoccurrence and are currently investigating this incident..

Jun 24, 21:58:08 GMT+0
Resolved - This incident has been resolved. Job queue times are nominal. We pinpointed the secondary factor as an issue with a specific cloud provider and shifted load..