Resuelto · duró 1 h
Caída de GitHub el 1 de octubre
Los informes de GitHub subieron a 235 por hora y se mantuvieron altos durante 1 h.
- Inicio
- 1:00 p.m.
- 1 de octubre de 2026 · UTC
- De vuelta a la normalidad
- 2:00 p.m.
- 1 h después
- Pico
- 235/h
- 5× lo normal
- Incidente de GitHub
- 20 min
- Elevated request latency
Informes durante la caída
Lo que dijo GitHub
www.githubstatus.comElevated request latency
- Resuelto · 1:57 p.m.
On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.
- Supervisando · 1:51 p.m.
The degradation has been mitigated. We are monitoring to ensure stability.
- Investigando · 1:39 p.m.
We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.
- Investigando · 1:37 p.m.
We are investigating reports of impacted performance for some GitHub services.
GitHub publicó su primera actualización 38 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.