Is GitHub down? › Outage history › Oct 5, 2026

GitHub outage on Oct 5, 2026: what happened

On Oct 5, 2026, the GitHub status page reported "Incident with Actions". About 3 hours 38 min: from Oct 5, 2026, 19:11 UTC to Oct 5, 2026, 22:49 UTC, by the official start and resolution times.

Started

Oct 5, 2026, 19:11 UTC

Resolved

Oct 5, 2026, 22:49 UTC

Duration

3 hours 38 min

Official impact

Critical

Affected

Actions, Pages

Source

Incident with Actions on the GitHub status page

The GitHub status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

What caused the GitHub outage?

"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."

From the GitHub status page, Oct 5, 2026, 22:49 UTC.

When was it fixed?

The GitHub status page marked it resolved at Oct 5, 2026, 22:49 UTC, 3 hours 38 min after it started. Its resolution note: "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 ..."

Timeline of official updates

Every update the GitHub status page posted, oldest first. Times are UTC.

1. Oct 5, 2026, 19:11 UTC investigating

   We are investigating reports of degraded performance for Actions

2. Oct 5, 2026, 19:15 UTC 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.

3. Oct 5, 2026, 19:50 UTC 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.

4. Oct 5, 2026, 20:39 UTC 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.

5. Oct 5, 2026, 20:47 UTC investigating

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

6. Oct 5, 2026, 21:09 UTC 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.

7. Oct 5, 2026, 21:22 UTC investigating

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

8. Oct 5, 2026, 21:31 UTC investigating

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

9. Oct 5, 2026, 21:32 UTC 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.

10. Oct 5, 2026, 21:54 UTC investigating

    Actions is operating normally.

11. Oct 5, 2026, 22:40 UTC investigating

    Pages is operating normally.

12. Oct 5, 2026, 22:49 UTC 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.

GitHub outage questions

Other recent GitHub incidents

• Delays for Pull Requests and Webhook deliveries Oct 21, 2026, 14:52 UTC, 4 hours 30 min
• Degraded availability for GitHub Actions, GitHub Pages and Webhooks Oct 19, 2026, 15:49 UTC, 1 hour 8 min
• CCA Automations are delayed when starting an Automation Oct 15, 2026, 18:31 UTC, 24 minutes
• [Retroactive] Actions workflow run logs delayed Oct 14, 2026, 00:12 UTC, duration not stated
• Incident with Actions, Pull Requests and Issues Oct 12, 2026, 12:21 UTC, 7 hours 54 min
• Incident with Git Operations, Issues, Actions and Pull Requests Oct 7, 2026, 17:17 UTC, 48 minutes

Full GitHub outage history and biggest outages → · Recent outages across all services →

Quotes are the GitHub status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with GitHub. Times are UTC.