Incident with Pull Requests and Issues
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
- minor
- Registro del proveedor creado
- 12 Aug 2026, 16:16:18 UTC
- Registro del proveedor actualizado
- 18 Aug 2026, 15:52:05 UTC
- Inicio explícito del proveedor
- 12 Aug 2026, 16:16:17 UTC
- Fin explícito del proveedor
- 12 Aug 2026, 16:41:18 UTC
Componentes afectados reportados por el proveedor
- Pull Requests
hhtssxt0f5v2 - Issues
kr09ddfgbfsf
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
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.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - monitoring
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.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting Issues and Pull Requests 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 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.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for Issues and Pull Requests
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC