Resuelto · duró 13 h

Caída de GitHub el 12 de agosto

Los informes de GitHub subieron a 2,681 por hora y se mantuvieron altos durante 13 h.

Inicio
3:00 p.m.
12 de agosto de 2026 · UTC
De vuelta a la normalidad
4:00 a.m.
13 h después
Pico
2,681/h
58× lo normal
Incidente de GitHub
25 min
Incident with Pull Requests and Issues

Informes durante la caída

1:00 p.m.5:50 a.m. UTC

Lo que dijo GitHub

www.githubstatus.com
Resuelto4:16–4:41 p.m. · 25 min

Incident with Pull Requests and Issues

  1. Resuelto · 4:41 p.m.

    Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.

  2. Supervisando · 4:38 p.m.

    We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.

  3. Supervisando · 4:35 p.m.

    The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

  4. Investigando · 4:24 p.m.

    We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

  5. Investigando · 4:16 p.m.

    We are investigating reports of degraded performance for Issues and Pull Requests

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

Lo que dijeron los usuarios

  • Maycoll4:23 p.m.

    no sive para subir cambios entre ramas

  • yo7:54 p.m.

    503 Service Unavailable

2 comentarios durante la caída

¿Está GitHub caído ahora mismo?

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

Estado de GitHub ahora →