INCIDENT OFICIAL ARCHIVADO

Incident with Actions

GitHub · Último estado guardado del proveedor: resolved

Informe actual del servicio →

El texto de la fuente oficial se muestra en su idioma original.

Es evidencia histórica.

El último estado guardado de un evento no es el estado actual del servicio. Las listas de fuentes pueden ser incompletas, y desaparecer de una fuente no confirma recuperación. Abre el informe actual o la fuente oficial para obtener evidencia más reciente.

Detalles de evento guardados

Estado del proveedor
resolved
Impacto del proveedor
critical
Registro del proveedor creado
05 Oct 2026, 19:11:58 UTC
Registro del proveedor actualizado
06 Oct 2026, 22:48:02 UTC
Inicio explícito del proveedor
05 Oct 2026, 19:11:58 UTC
Fin explícito del proveedor
05 Oct 2026, 22:49:42 UTC

Componentes afectados reportados por el proveedor

  • Actions br0l2tvcx85d
  • Pages vg70hn9s2tyj

Estas asociaciones describen el alcance reportado del evento. No establecen disponibilidad actual de componentes ni dependencias verificadas.

La hora de creación de un registro no es necesariamente el inicio de una interrupción. Las horas no reportadas siguen sin estar disponibles. No calculamos el tiempo de inactividad a partir de las horas de recopilación.

Actualizaciones del proveedor en revisiones guardadas

Más recientes primero. Mostramos hasta 100 actualizaciones distintas de las últimas 20 revisiones de contenido guardadas. Las modificaciones de redacción a la misma hora del proveedor se conservan por separado.

  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 en una revisión guardada a las 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 en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC
  3. investigating

    Pages is operating normally.

    Visto en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC
  4. investigating

    Actions is operating normally.

    Visto en una revisión guardada a las 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 en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC
  6. investigating

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

    Visto en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC
  7. investigating

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

    Visto en una revisión guardada a las 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 en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC
  9. investigating

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

    Visto en una revisión guardada a las 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 en una revisión guardada a las 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 en una revisión guardada a las 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 en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC
  13. investigating

    We are investigating reports of degraded performance for Actions

    Visto en una revisión guardada a las 06 Oct 2026, 22:48:58 UTC