GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Actions

ResolvedcriticalOfficial source confirmedSpecific component onlyFirst recorded update Oct 5, 2026, 07:11 PM · Resolved Oct 5, 2026, 10:49 PM

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. <br /><br /> <br />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...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

ActionsPages

Updates (12)

  1. Oct 5, 2026, 10:49 PM
    Incident with Actions

    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. <br /><br /> <br />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 l

    GitHub ↗
  2. Oct 5, 2026, 10:40 PM
    Incident with Actions

    Pages is operating normally.

    GitHub ↗
  3. Oct 5, 2026, 09:54 PM
    Incident with Actions

    Actions is operating normally.

    GitHub ↗
  4. Oct 5, 2026, 09:32 PM
    Incident with Actions

    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.

    GitHub ↗
  5. Oct 5, 2026, 09:31 PM
    Incident with Actions

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

    GitHub ↗
  6. Oct 5, 2026, 09:22 PM
    Incident with Actions

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

    GitHub ↗
  7. Oct 5, 2026, 09:09 PM
    Incident with Actions

    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.

    GitHub ↗
  8. Oct 5, 2026, 08:47 PM
    Incident with Actions

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

    GitHub ↗
  9. Oct 5, 2026, 08:39 PM
    Incident with Actions

    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.

    GitHub ↗
  10. Oct 5, 2026, 07:50 PM
    Incident with Actions

    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.

    GitHub ↗
  11. Oct 5, 2026, 07:15 PM
    Incident with Actions

    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.

    GitHub ↗
  12. Oct 5, 2026, 07:11 PM
    Incident with Actions

    We are investigating reports of degraded performance for Actions

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.