Resuelto · duró 1 h

Caída de GitHub el 26 de octubre

Los informes de GitHub subieron a 150 por hora y se mantuvieron altos durante 1 h.

Inicio: 6:00 p.m.; 26 de octubre de 2026 · UTC
De vuelta a la normalidad: 7:00 p.m.; 1 h después
Pico: 150/h; 3× lo normal
Incidente de GitHub: 9 min; Incident with Actions, Issues, API Requests and Pull Requests

Informes durante la caída

4:00 p.m.8:50 p.m. UTC

Resuelto6:48–6:57 p.m. · 9 min

Incident with Actions, Issues, API Requests and Pull Requests

Resuelto · 6:57 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.
Supervisando · 6:54 p.m.
We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.<br /><br />We mitigated the issue and all services have recovered.
Supervisando · 6:50 p.m.
The degradation has been mitigated. We are monitoring to ensure stability.
Investigando · 6:48 p.m.
We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests

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

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