Codecov Outage History

Codecov is up right now

Pingoru has recorded 50 incidents for Codecov: 20 in the last 12 months and 2 in the last 90 days.

Source: status.codecov.io

50incidents recorded
20last 12 months
2last 90 days
11 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Codecov in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202620 of 720 (0%)
May 202600 of 744 (0%)
June 202610 of 720 (0%)
July 2026529 of 744 (4%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 202612 of 744 (0%)
November 202600 of 85 (0%)

Incidents, newest first

Critical October 5, 2026 Codecov app and services are down 2h 22m Codecov Frontend, Codecov Backend

Started Oct 05, 2026, 06:53 AM UTC· resolved Oct 05, 2026, 09:15 AM UTC

  1. investigating Oct 05, 2026, 06:53 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 05, 2026, 06:54 AM UTC

    We are continuing to investigate the issue

  3. identified Oct 05, 2026, 06:55 AM UTC

    Codecov services have become unavailable because of an SSL certificate expiration. We are currently working to remedy this issue.

  4. identified Oct 05, 2026, 07:11 AM UTC

    We are continuing to work on a fix for this issue.

  5. identified Oct 05, 2026, 07:25 AM UTC

    We are continuing to work on a fix for this issue.

  6. identified Oct 05, 2026, 07:45 AM UTC

    We are continuing to work on a fix for this issue.

  7. identified Oct 05, 2026, 08:09 AM UTC

    We are continuing to work on a fix for this issue.

  8. identified Oct 05, 2026, 08:24 AM UTC

    We are continuing to work on a fix for this issue.

  9. monitoring Oct 05, 2026, 08:33 AM UTC

    A fix has been implemented and we are monitoring the results.

  10. monitoring Oct 05, 2026, 08:33 AM UTC

    We are continuing to monitor for any further issues.

  11. monitoring Oct 05, 2026, 09:02 AM UTC

    We are continuing to monitor for any further issues.

  12. monitoring Oct 05, 2026, 09:03 AM UTC

    We are continuing to monitor for any further issues.

  13. resolved Oct 05, 2026, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 Degraded performance on report processing 49m Codecov Backend

Started Aug 13, 2026, 04:01 PM UTC· resolved Aug 13, 2026, 04:51 PM UTC

  1. investigating Aug 13, 2026, 04:01 PM UTC

    We are currently investigating this issue.

  2. identified Aug 13, 2026, 04:02 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 13, 2026, 04:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 13, 2026, 04:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 26, 2026 PR Notifications delayed 32m

Started Jul 26, 2026, 02:48 AM UTC· resolved Jul 26, 2026, 03:20 AM UTC

  1. resolved Jul 26, 2026, 02:30 AM UTC

    Server OOM caused drop in PR notifications between 10:48PM ET to 11:20PM ET. PRs expecting notifications during that period have now been manually sent.

Read the full incident report →

Major July 22, 2026 Upload processing is severely delayed 5h 57m Codecov Backend

Started Jul 22, 2026, 03:02 PM UTC· resolved Jul 22, 2026, 09:00 PM UTC

  1. investigating Jul 22, 2026, 03:02 PM UTC

    We are currently investigating this issue.

  2. identified Jul 22, 2026, 03:44 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 22, 2026, 03:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. investigating Jul 22, 2026, 04:36 PM UTC

    We are currently investigating this issue.

  5. investigating Jul 22, 2026, 04:57 PM UTC

    Changes previously implemented showed some improvement, but the issue remains and needs further investigation. Harness coverage team is currently working on additional investigation and changes.

  6. identified Jul 22, 2026, 06:12 PM UTC

    The issue has been identified and a fix is being implemented.

  7. identified Jul 22, 2026, 07:34 PM UTC

    We are continuing to work on a fix for this issue.

  8. identified Jul 22, 2026, 07:39 PM UTC

    The issue has been identified as a an issue with Codecov's redis instance. We are working on a fix.

  9. monitoring Jul 22, 2026, 08:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  10. monitoring Jul 22, 2026, 08:17 PM UTC

    The backlog of tasks is clearing at a consistent rate. We will continue monitoring the situation.

  11. monitoring Jul 22, 2026, 08:37 PM UTC

    The backlog of tasks is continuing to clear, users affected in the early stages of the incident should expect to see their notifications.

  12. resolved Jul 22, 2026, 09:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2026 Codecov services partially impacted and causing slowdowns 12h 46m

Started Jul 16, 2026, 04:42 PM UTC· resolved Jul 17, 2026, 05:29 AM UTC

  1. investigating Jul 16, 2026, 04:42 PM UTC

    We are currently investigating this issue.

  2. identified Jul 16, 2026, 04:48 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 16, 2026, 07:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 17, 2026, 05:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 15, 2026 Degraded processing service 6h 54m

Started Jul 15, 2026, 05:29 PM UTC· resolved Jul 16, 2026, 12:24 AM UTC

  1. investigating Jul 15, 2026, 05:29 PM UTC

    We are currently investigating this issue. Users may see significant delays in coverage notifications on pull requests

  2. identified Jul 15, 2026, 05:30 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 15, 2026, 05:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 16, 2026, 12:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Codecov UI showing 400 Bad Request 3h 2m Codecov Frontend

Started Jul 08, 2026, 03:42 PM UTC· resolved Jul 08, 2026, 06:45 PM UTC

  1. investigating Jul 08, 2026, 03:42 PM UTC

    We are currently investigating this issue.

  2. identified Jul 08, 2026, 03:43 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 08, 2026, 04:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 08, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 6, 2026 Codecov uploaders (Action/Orb/Step) fail gpg verification –

Started Jun 06, 2026, 01:00 PM UTC· resolved Jun 06, 2026, 01:00 PM UTC

  1. resolved Jun 06, 2026, 01:00 PM UTC

    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.

Read the full incident report →

Minor April 23, 2026 Integrity verification on the CLI/Action is failing and blocking uploads to Codecov 19m

Started Apr 23, 2026, 02:13 PM UTC· resolved Apr 23, 2026, 02:33 PM UTC

  1. investigating Apr 23, 2026, 02:13 PM UTC

    We are currently investigating the issue.

  2. identified Apr 23, 2026, 02:15 PM UTC

    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.

  3. monitoring Apr 23, 2026, 02:15 PM UTC

    The cache has been purged and we are monitoring the issue.

  4. resolved Apr 23, 2026, 02:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026 Notifications might be delayed 48m Codecov Backend

Started Apr 15, 2026, 04:27 PM UTC· resolved Apr 15, 2026, 05:15 PM UTC

  1. investigating Apr 15, 2026, 04:27 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 15, 2026, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 22, 2026 Coverage notifications delayed 16h 55m

Started Mar 22, 2026, 02:07 PM UTC· resolved Mar 23, 2026, 07:03 AM UTC

  1. investigating Mar 22, 2026, 02:07 PM UTC

    We are currently investigating the issue.

  2. identified Mar 22, 2026, 07:25 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 22, 2026, 08:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 23, 2026, 07:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2026 Coverage notifications delayed 7h 7m Codecov Backend

Started Mar 20, 2026, 08:57 PM UTC· resolved Mar 21, 2026, 04:05 AM UTC

  1. investigating Mar 20, 2026, 08:57 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 21, 2026, 04:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 19, 2026 Coverage notifications delayed 1d Codecov Backend

Started Mar 19, 2026, 07:22 PM UTC· resolved Mar 20, 2026, 07:30 PM UTC

  1. investigating Mar 19, 2026, 07:22 PM UTC

    We are currently investigating this issue. Status and comment notifications are being reported as highly delayed

  2. monitoring Mar 19, 2026, 07:23 PM UTC

    A fix has been implemented and we are monitoring the results

  3. monitoring Mar 20, 2026, 07:53 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 20, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 16, 2026 Unable to login with Bitbucket 1d 4h Codecov Frontend

Started Mar 16, 2026, 11:46 AM UTC· resolved Mar 17, 2026, 04:07 PM UTC

  1. investigating Mar 16, 2026, 11:46 AM UTC

    With identified an issue with our OAuth connection for Bitbucket

  2. monitoring Mar 17, 2026, 02:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 17, 2026, 04:07 PM UTC

    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.

Read the full incident report →

Minor March 10, 2026 Upload Processing Queue Slowdown 4h 58m Codecov Backend

Started Mar 10, 2026, 09:44 PM UTC· resolved Mar 11, 2026, 02:42 AM UTC

  1. investigating Mar 10, 2026, 09:44 PM UTC

    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.

  2. resolved Mar 11, 2026, 02:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 26, 2026 Upload Processing Queue Slowdown 10h 36m Codecov Backend

Started Feb 26, 2026, 09:20 PM UTC· resolved Feb 27, 2026, 07:56 AM UTC

  1. investigating Feb 26, 2026, 09:20 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 26, 2026, 10:26 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 26, 2026, 10:39 PM UTC

    We have identified the issue and are deploying a fix.

  4. investigating Feb 26, 2026, 11:47 PM UTC

    We are continuing to investigate this issue.

  5. identified Feb 27, 2026, 12:27 AM UTC

    We have identified a solution and are deploying a fix.

  6. monitoring Feb 27, 2026, 12:39 AM UTC

    A fix has been implemented and we are monitoring the results.

  7. monitoring Feb 27, 2026, 01:12 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved Feb 27, 2026, 07:56 AM UTC

    This incident has been resolved. We will continue monitoring for any changes.

Read the full incident report →

Major February 19, 2026 Upload Processing Queue Slowdown –

Started Feb 19, 2026, 03:00 AM UTC· resolved Feb 19, 2026, 03:00 AM UTC

  1. resolved Feb 19, 2026, 03:00 AM UTC

    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.

Read the full incident report →

Notice December 9, 2025 Slower Processing Bundle Analysis 2d 5h Codecov Backend

Started Dec 09, 2025, 08:54 AM UTC· resolved Dec 11, 2025, 02:42 PM UTC

  1. monitoring Dec 09, 2025, 08:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Dec 11, 2025, 02:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 Slower processing 21h 4m Codecov Backend

Started Nov 18, 2025, 07:14 PM UTC· resolved Nov 19, 2025, 04:18 PM UTC

  1. investigating Nov 18, 2025, 07:14 PM UTC

    We are currently investigating this issue.

  2. monitoring Nov 18, 2025, 08:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 19, 2025, 04:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025 Cli uploader download issues 3h 26m

Started Nov 18, 2025, 02:33 PM UTC· resolved Nov 18, 2025, 05:59 PM UTC

  1. investigating Nov 18, 2025, 02:33 PM UTC

    Cloudflare is having issues and that impacts the codecov cli

  2. resolved Nov 18, 2025, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 30, 2025 Login to Codecov via Sentry button degraded 30m Codecov Frontend

Started Oct 30, 2025, 01:40 PM UTC· resolved Oct 30, 2025, 02:11 PM UTC

  1. investigating Oct 30, 2025, 01:40 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 30, 2025, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 14, 2025 Codecov AI Commands 1d 3h Codecov Backend

Started Oct 14, 2025, 04:34 PM UTC· resolved Oct 15, 2025, 08:03 PM UTC

  1. investigating Oct 14, 2025, 04:34 PM UTC

    It's affecting the PR ai commands @codecov-ai-reviewer review and @codecov-ai-reviewer test

  2. resolved Oct 15, 2025, 08:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 9, 2025 Test Analytics are down 6d

Started Oct 09, 2025, 01:00 AM UTC· resolved Oct 15, 2025, 01:18 AM UTC

  1. investigating Oct 09, 2025, 01:00 AM UTC

    Test Analytics are down

  2. resolved Oct 15, 2025, 01:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 2, 2025 SSL issue 2h 37m Codecov Frontend

Started Sep 02, 2025, 05:59 PM UTC· resolved Sep 02, 2025, 08:37 PM UTC

  1. investigating Sep 02, 2025, 05:59 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 02, 2025, 08:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2025 Generalized latency issues throughout infrastructure 2h 25m Codecov Backend

Started Jun 12, 2025, 06:37 PM UTC· resolved Jun 12, 2025, 09:03 PM UTC

  1. investigating Jun 12, 2025, 06:37 PM UTC

    We are currently investigating latency problems across all of our infrastructure in US regions.

  2. identified Jun 12, 2025, 06:38 PM UTC

    We have identified the problem as being with our cloud infrastructure provider and have contacted them for further diagnosis. Customer impact is delays in ingestion and intermittent failures for both US customers.

  3. monitoring Jun 12, 2025, 08:11 PM UTC

    Some of the our cloud infrastructure provider features are back online.

  4. resolved Jun 12, 2025, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →