Critical impactResolvedDevOps

GitHub outage: Incident with Actions

GitHub reported this critical-impact incident on its official status page on Oct 5, 2026, 19:11 UTC. It was resolved after 3h 38m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Oct 5, 2026, 19:11 UTC
started
Oct 5, 2026, 22:49 UTC
resolved
3h 38m
duration
Critical
impact

Affected components

  • Actions
  • Pages
  1. resolvedOct 5, 2026, 22:49 UTC

    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.

  2. investigatingOct 5, 2026, 22:40 UTC

    Pages is operating normally.

  3. investigatingOct 5, 2026, 21:54 UTC

    Actions is operating normally.

  4. investigatingOct 5, 2026, 21:32 UTC

    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.

  5. investigatingOct 5, 2026, 21:31 UTC

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

  6. investigatingOct 5, 2026, 21:22 UTC

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

  7. investigatingOct 5, 2026, 21:09 UTC

    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.

  8. investigatingOct 5, 2026, 20:47 UTC

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

  9. investigatingOct 5, 2026, 20:39 UTC

    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.

  10. investigatingOct 5, 2026, 19:50 UTC

    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.

  11. investigatingOct 5, 2026, 19:15 UTC

    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.

  12. investigatingOct 5, 2026, 19:11 UTC

    We are investigating reports of degraded performance for Actions

What APIStatus.watch saw

  • Oct 5, 2026, 19:13 UTCoperational → degraded
  • Oct 5, 2026, 20:48 UTCdegraded → partial outage
  • Oct 5, 2026, 21:33 UTCpartial outage → degraded
  • Oct 5, 2026, 22:43 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history