Resuelto · duró 3 h

Caída de GitHub el 22 de octubre

Los informes de GitHub subieron a 235 por hora y se mantuvieron altos durante 3 h.

Inicio
2:00 p.m.
22 de octubre de 2026 · UTC
De vuelta a la normalidad
5:00 p.m.
3 h después
Pico
235/h
5× lo normal
Incidente de GitHub
1 h 01 min
Incident with Actions

Informes durante la caída

12:00 p.m.6:50 p.m. UTC

Lo que dijo GitHub

www.githubstatus.com
Resuelto2:18–3:18 p.m. · 1 h 01 min

Incident with Actions

  1. Resuelto · 3:18 p.m.

    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. Supervisando · 3:18 p.m.

    GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.

  3. Supervisando · 3:17 p.m.

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  4. Investigando · 3:06 p.m.

    We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.

  5. Investigando · 2:35 p.m.

    Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.

  6. Investigando · 2:19 p.m.

    We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.

  7. Investigando · 2:18 p.m.

    We are investigating reports of degraded performance for Actions

GitHub publicó su primera actualización 18 min después de que los informes comenzaran a subir.

¿Está GitHub caído ahora mismo?

Estado en vivo, informes de hoy y otras caídas anteriores.

Estado de GitHub ahora →