https://www.githubstatus.com/incidents/qcvjkzcs7j74 Help Community Status GitHub.com GitHub header GitHub header Subscribe to UpdatesSubscribe x Get email notifications whenever GitHub creates, updates or resolves an incident. Email address: [ ] Enter OTP: [ ] Resend OTP in: seconds Didn't receive the OTP? Resend OTP [Subscribe via Email] By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get text message notifications whenever GitHub creates or resolves an incident. Country code: [United States (+1) ] Phone number: [ ] Change number Enter OTP: [ ] Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP [Subscribe via Text Message] Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy. Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: [ ] The URL we should send the webhooks to Email address: [ ] We'll send you email if your endpoint fails [Subscribe] By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Visit our support site. Get the Atom Feed or RSS Feed. Incident with Actions Incident Report for GitHub 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. Posted Aug 07, 2026 - 02:04 UTC Update 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. 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. 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. Posted Aug 07, 2026 - 02:03 UTC Update 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. Posted Aug 07, 2026 - 00:59 UTC Monitoring The degradation has been mitigated. We are monitoring to ensure stability. Posted Aug 07, 2026 - 00:06 UTC Update The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Posted Aug 07, 2026 - 00:05 UTC Update 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. 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. We are monitoring all affected services for sustained recovery and will provide another update shortly. Posted Aug 07, 2026 - 00:01 UTC Update 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. 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. We are monitoring all affected services for sustained recovery and will provide another update shortly. Posted Aug 07, 2026 - 00:01 UTC Update 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. 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. GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused. We continue to monitor recovery across all affected services and will provide another update as conditions improve. Posted Aug 06, 2026 - 23:13 UTC Update 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. 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. GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused. We are continuing to monitor recovery and will provide another update as conditions improve. Posted Aug 06, 2026 - 22:18 UTC Update 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. 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. 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. Posted Aug 06, 2026 - 21:30 UTC Update 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. 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. Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Posted Aug 06, 2026 - 20:34 UTC Update We are continuing to work on an issue affecting GitHub Actions. 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. Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. Our engineers remain actively engaged. Posted Aug 06, 2026 - 19:43 UTC Update We are continuing to work on an issue affecting multiple GitHub services. 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. Customers using self-hosted runners may see errors or rate limiting when runners register. Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. Recovery is taking longer than we expected, and engineers remain actively engaged. Posted Aug 06, 2026 - 18:46 UTC Update We are continuing to work on an issue affecting multiple GitHub services. Workflow runs are still failing or delayed in starting, and some queued jobs may time out. Customers using self-hosted runners may see errors or rate limiting when runners register. Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. Engineers have applied further mitigations and are continuing to work towards full recovery. Posted Aug 06, 2026 - 18:11 UTC Update We are continuing to work on an issue affecting multiple GitHub services. Workflow runs are failing or delayed in starting, and some queued jobs may time out. Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected. Webhook deliveries may be delayed. Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now. Posted Aug 06, 2026 - 17:40 UTC Update We are continuing to work on the issue affecting GitHub Actions. Workflow runs are still failing or delayed in starting, and some queued jobs may time out. Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures. Our engineers have applied several mitigations and are rolling out a further fix now. Posted Aug 06, 2026 - 17:02 UTC Update Actions and Pages are experiencing degraded availability. We are continuing to investigate. Posted Aug 06, 2026 - 16:33 UTC Update We are continuing to work on the issue affecting GitHub Actions. Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may also see failures. Engineers are actively working towards full recovery. Posted Aug 06, 2026 - 16:27 UTC Update Pages is experiencing degraded performance. We are continuing to investigate. Posted Aug 06, 2026 - 16:27 UTC Update Pages is operating normally. Posted Aug 06, 2026 - 16:19 UTC Update Pages is experiencing degraded performance. We are continuing to investigate. Posted Aug 06, 2026 - 15:53 UTC Update 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. Some customers may also see unexpected rate limiting in their workflows. Engineers have identified the source of the disruption and are actively working on a mitigation Posted Aug 06, 2026 - 15:45 UTC Update Actions is experiencing degraded availability. We are continuing to investigate. Posted Aug 06, 2026 - 15:41 UTC Investigating We are investigating reports of degraded performance for Actions Posted Aug 06, 2026 - 15:22 UTC This incident affected: Actions and Pages. - Current Status Powered by Atlassian Statuspage GitHub footer Subscribe to our developer newsletter Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe Product * Features * Enterprise * Copilot * Security * Pricing * Team * Resources * Roadmap * Compare GitHub Platform * Developer API * Partners * Education * GitHub CLI * GitHub Desktop * GitHub Mobile Support * Docs * Community Forum * Professional Services * Skills * Contact GitHub Company * About * Customer stories * Blog * The ReadME Project * Careers * Newsroom * Inclusion * Social Impact * Shop * (c) GitHub, Inc. * Terms * Privacy (Updated 08/2022) * * * * * * * x Subscribe to Incident Subscribe to updates for Incident with Actions via email and/or text message. You'll receive email notifications when incidents are updated, and text message notifications whenever GitHub creates or resolves an incident. VIA EMAIL: [ ] VIA SMS: [United States (+1) ] Enter mobile number [ ] Edit number Send OTP Enter the OTP sent [ ] Resend OTP in 30 seconds To receive SMS updates, please verify your number. To proceed with just email click 'Subscribe' Subscribe to Incident Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.