Disruption with GitHub Billing
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
- 26 Aug 2026, 23:37:20 UTC
- Registro del proveedor actualizado
- 31 Aug 2026, 22:46:13 UTC
- Inicio explícito del proveedor
- 26 Aug 2026, 23:37:20 UTC
- Fin explícito del proveedor
- 27 Aug 2026, 19:44:08 UTC
Componentes afectados reportados por el proveedor
El proveedor indicó explícitamente que no había componentes afectados en esta revisión guardada.
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
On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). <br /><br />This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. <br /><br />We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC