INCIDENT OFICIAL ARCHIVADO

Incident with Copilot

GitHub · Último estado guardado del proveedor: resolved

Informe actual del servicio →

El texto de la fuente oficial se muestra en su idioma original.

Es evidencia histórica.

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
03 Aug 2026, 09:53:27 UTC
Registro del proveedor actualizado
12 Aug 2026, 15:00:05 UTC
Inicio explícito del proveedor
03 Aug 2026, 09:53:27 UTC
Fin explícito del proveedor
03 Aug 2026, 11:25:12 UTC

Componentes afectados reportados por el proveedor

  • Copilot pjmpxvq2cmr2

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.

  1. resolved

    On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak-traffic periods, at times approaching 100% for the affected internal lookups. Approximately 4,066 users were affected in a single 60-minute window, concentrated among IDE-based clients. The underlying AI models themselves remained healthy throughout.<br /><br />The incident was caused by an increase in how often clients requested the model list, which pushed an internal user-authorization lookup past a rate limit; the rate-limited responses were surfaced to users as errors. We mitigated the impact by increasing how long Copilot caches that authorization lookup, which reduced load on the internal service, and we have additional capacity and rate-limit changes in progress. To prevent recurrence we are improving monitoring for this class of failure, adjusting cache and rate-limit settings, and coordinating with client teams on request patterns.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC
  2. monitoring

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

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC
  3. investigating

    We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC
  4. investigating

    We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC
  5. investigating

    We are investigating reports of degraded performance for Copilot

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC