56 Codecov incidents · 2024年1月 — 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.
服务器OOM导致PR通知在10:48PM ET到11:20PM ET之间下降. 在此期间,预计会收到通知的公关已经用人工方式发出.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
以往实施的改革有所改进,但问题仍然存在并需要进一步调查。 优势覆盖小组目前正在着手进行更多的调查和改革.
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
这个问题被确定为与Codecov的再现案例相提并论的问题. 我们正在努力解决问题.
一项措施已经执行,我们正在监测结果.
积压的任务正在以一致的速度清理。 我们将继续监测局势.
积压的任务正在继续清理,在事故早期阶段受到影响的用户应该看到其通知.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题。 用户可能会发现,根据抽取请求,覆盖通知出现重大延误
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.