56 Codecov incidents · enero de 2024 — official updates, affected components, duration and resolution details.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Server OOM causó la caída en notificaciones de PR entre 10:48PM ET a 11:20PM ET. Los PR que esperan notificaciones durante ese período han sido enviados manualmente.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando esta cuestión.
Los cambios aplicados anteriormente mostraron cierta mejora, pero la cuestión sigue siendo y necesita más investigación. El equipo de cobertura de daños está trabajando en investigaciones y cambios adicionales.
Se ha determinado la cuestión y se está aplicando una solución.
Seguimos trabajando en una solución para esta cuestión.
El tema ha sido identificado como un problema con la instancia roja de Codecov. Estamos trabajando en una solución.
Se ha aplicado una solución y estamos monitoreando los resultados.
El atraso de las tareas está aclarando a un ritmo constante. Seguiremos vigilando la situación.
La acumulación de tareas sigue siendo clara, los usuarios afectados en las primeras etapas del incidente deben esperar ver sus notificaciones.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando esta cuestión.
Se ha determinado la cuestión y se está aplicando una solución.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando esta cuestión. Los usuarios pueden ver retrasos significativos en las notificaciones de cobertura en solicitudes de tiradas
Se ha determinado la cuestión y se está aplicando una solución.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando esta cuestión.
Se ha determinado la cuestión y se está aplicando una solución.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
On Saturday, June 6th, the Codecov gpg public key located at keybase.io/codecovsecurity was absent. This caused widespread outages for users uploading with the Codecov - GitHub Action - CircleCI Orb - Bitrise Step In order to quickly move and prevent further outages, the Codecov team deleted the `codecovsecurity` account and created `codecovsecops` with the same public gpg key. This key can be verified against any pre-existing CLI to prove it is the same key and also at about.codecov.io/security. The key location was updated in all of the above uploaders on the latest versions.
We are currently investigating the issue.
We have identified the issue. There is no security implication for this issue, the releases were re-published and the cache is currently being cleared.
The cache has been purged and we are monitoring the issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue. Status and comment notifications are being reported as highly delayed
A fix has been implemented and we are monitoring the results
We are continuing to monitor for any further issues.
This incident has been resolved.
With identified an issue with our OAuth connection for Bitbucket
A fix has been implemented and we are monitoring the results.
This incident has been resolved. All Bitbucket users will need to login to Codecov again, as their authorizations were reset. Codecov will not be able to commincate with Bitbucket until you do.
We are experiencing a slowdown in upload processing. This issue has been happening intermittently for the past few days. We are currently investigating the issue.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue and are deploying a fix.
We are continuing to investigate this issue.
We have identified a solution and are deploying a fix.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved. We will continue monitoring for any changes.
We have identified a backlog in our processing queues that is causing delays in coverage report processing. Uploads are still being accepted but results may take longer than expected to appear. Our team is actively working to remediate the issue. No data has been lost. *Update 2026-02-24 5PM PT* The issue has been identified and patched, we will continue to monitor for any changes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is having issues and that impacts the codecov cli
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.