56 Codecov incidents · janvier 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 a provoqué une baisse des notifications PR entre 10:48PM ET et 23:20PM ET. Les PR qui attendent des notifications pendant cette période ont maintenant été envoyées manuellement.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur cette question.
Les changements précédemment mis en œuvre ont montré une certaine amélioration, mais la question demeure et doit être examinée plus avant. L'équipe de couverture de Harness travaille actuellement à des enquêtes supplémentaires et à des changements.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Nous continuons de travailler sur une solution à ce problème.
Le problème a été identifié comme un problème avec l'instance de redis de Codecov. Nous travaillons sur une solution.
Un correctif a été mis en place et nous suivons les résultats.
L'arriéré des tâches est en train de se résorber à un rythme constant. Nous continuerons de suivre la situation.
L'arriéré de tâches continue de s'effacer, les utilisateurs touchés au début de l'incident devraient s'attendre à voir leurs notifications.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur cette question.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur cette question. Les utilisateurs peuvent voir des retards importants dans les notifications de couverture sur les demandes de retrait
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur cette question.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.