Incident with Actions
GitHub · Último estado guardado del proveedor: resolved
El texto de la fuente oficial se muestra en su idioma original.
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
- major
- Registro del proveedor creado
- 29 Jul 2026, 15:26:24 UTC
- Registro del proveedor actualizado
- 30 Jul 2026, 01:28:07 UTC
- Inicio explícito del proveedor
- 29 Jul 2026, 15:26:24 UTC
- Fin explícito del proveedor
- 29 Jul 2026, 16:00:54 UTC
Componentes afectados reportados por el proveedor
- Actions
br0l2tvcx85d
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.
- resolved
On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded availability for Actions
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC