Incident with GraphQL API Requests
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
- 11 Aug 2026, 14:50:40 UTC
- Registro del proveedor actualizado
- 12 Aug 2026, 19:30:45 UTC
- Inicio explícito del proveedor
- 11 Aug 2026, 14:50:40 UTC
- Fin explícito del proveedor
- 11 Aug 2026, 20:06:56 UTC
Componentes afectados reportados por el proveedor
- API Requests
brv1bkgrwx7q
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 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. <br /><br />This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck. <br /><br />We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - monitoring
We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting API 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 have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when 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 API Requests
Visto en una revisión guardada a las 06 Oct 2026, 13:58:39 UTC