GitHub Status

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.

Monitoring: Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

Monitoring: We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: Git Operations is operating normally.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded availability. We are continuing to investigate.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

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.

Monitoring: All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.

Investigating: We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

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.

Investigating: We are deploying a mitigation and plan to resume migrations shortly thereafter

Investigating: We are working towards a mitigation that will allow us to resume processing enterprise migrations.

Investigating: All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.

Investigating: Pull Requests is operating normally.

Investigating: Webhooks is operating normally.

Investigating: We are investigating reports of degraded performance for Pull Requests and Webhooks

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.

Monitoring: Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

Monitoring: We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: Git Operations is operating normally.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded availability. We are continuing to investigate.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

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.

Monitoring: Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

Monitoring: We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: Git Operations is operating normally.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded availability. We are continuing to investigate.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

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.

Monitoring: All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.

Investigating: We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

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.

Investigating: We are deploying a mitigation and plan to resume migrations shortly thereafter

Investigating: We are working towards a mitigation that will allow us to resume processing enterprise migrations.

Investigating: All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.

Investigating: Pull Requests is operating normally.

Investigating: Webhooks is operating normally.

Investigating: We are investigating reports of degraded performance for Pull Requests and Webhooks

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.

Monitoring: Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

Monitoring: We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: Git Operations is operating normally.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded availability. We are continuing to investigate.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

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.

Monitoring: All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.

Investigating: We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

Resolved: On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes.


During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected.


The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services.


We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC.


We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.

Investigating: Pages is operating normally.

Investigating: Actions is operating normally.

Investigating: We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

Investigating: Pages is experiencing degraded performance. We are continuing to investigate.

Investigating: In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.

Investigating: Actions is experiencing degraded availability. We are continuing to investigate.

Investigating: We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.

Investigating: We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.

Investigating: We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.

Investigating: We are investigating reports of degraded performance for Actions

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.

Monitoring: Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

Monitoring: We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Investigating: We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Actions is operating normally.

Investigating: The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: Git Operations is operating normally.

Investigating: Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating: We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

Investigating: Git Operations is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded availability. We are continuing to investigate.

Investigating: Issues is experiencing degraded performance. We are continuing to investigate.

Investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

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.

Monitoring: All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

Monitoring: The degradation has been mitigated. We are monitoring to ensure stability.

Investigating: We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.

Investigating: We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

Resolved: On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes.


During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected.


The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services.


We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC.


We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.

Investigating: Pages is operating normally.

Investigating: Actions is operating normally.

Investigating: We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

Investigating: Pages is experiencing degraded performance. We are continuing to investigate.

Investigating: In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.

Investigating: Actions is experiencing degraded availability. We are continuing to investigate.

Investigating: We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.

Investigating: We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.

Investigating: We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.

Investigating: We are investigating reports of degraded performance for Actions