INCIDENT OFICIAL ARQUIVADO

Incident with Actions

GitHub · Último status salvo do provedor: resolved

Relatório atual do serviço →

O texto da fonte oficial é exibido no idioma original.

São evidências históricas.

O último status salvo de um evento não é o status atual do serviço. As listas das fontes podem ser incompletas, e desaparecer de uma fonte não confirma recuperação. Abra o relatório atual ou a fonte oficial para evidências mais recentes.

Detalhes de evento salvos

Status do provedor
resolved
Impacto do provedor
critical
Registro do provedor criado
05 Oct 2026, 19:11:58 UTC
Registro do provedor atualizado
06 Oct 2026, 22:48:02 UTC
Início explícito do provedor
05 Oct 2026, 19:11:58 UTC
Fim explícito do provedor
05 Oct 2026, 22:49:42 UTC

Componentes afetados informados pelo provedor

  • Actions br0l2tvcx85d
  • Pages vg70hn9s2tyj

Essas associações descrevem o escopo relatado do evento. Não estabelecem disponibilidade atual dos componentes ou dependências verificadas.

A hora de criação de um registro não é necessariamente o início de uma interrupção. Horários não informados permanecem indisponíveis. Não calculamos o tempo de indisponibilidade a partir das horas de coleta.

Atualizações do provedor em revisões salvas

Mais recentes primeiro. Exibimos até 100 atualizações distintas das últimas 20 revisões de conteúdo salvas. Alterações de texto no mesmo horário do provedor são mantidas separadamente.

  1. 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. <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 lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. <br /><br /><br />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. <br /><br /><br />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. <br /><br /> <br />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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  2. 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.

    Visto em uma revisão salva às 06 Oct 2026, 13:58:39 UTC
  3. investigating

    Pages is operating normally.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  4. investigating

    Actions is operating normally.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  5. 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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  6. investigating

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

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  7. investigating

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

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  8. 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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  9. investigating

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

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  10. 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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  11. 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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  12. 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.

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC
  13. investigating

    We are investigating reports of degraded performance for Actions

    Visto em uma revisão salva às 06 Oct 2026, 22:48:58 UTC