Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Codecov outage history

    57 recorded Codecov incidents since January 2024, with official updates, affected components, duration and resolution information.

    Back to current status

    Codecov app and services are down

    Started October 5, 2026 at 6:53 AM UTC · 2h 23m

    OutageCritical incident
    Affected components
    Codecov FrontendCodecov Backend
    1. October 5, 2026 at 6:53 AM UTCinvestigating

      We are currently investigating this issue.

    2. October 5, 2026 at 6:54 AM UTCinvestigating

      We are continuing to investigate the issue

    3. October 5, 2026 at 6:55 AM UTCidentified

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

    4. October 5, 2026 at 8:24 AM UTCidentified

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

    5. October 5, 2026 at 8:33 AM UTCmonitoring

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

    6. October 5, 2026 at 9:03 AM UTCmonitoring

      We are continuing to monitor for any further issues.

    7. October 5, 2026 at 9:15 AM UTCresolved

      This incident has been resolved.

    Degraded performance on report processing

    Started August 13, 2026 at 4:01 PM UTC · 50m

    IssuesMinor incident
    Affected components
    Codecov Backend
    1. August 13, 2026 at 4:01 PM UTCinvestigating

      We are currently investigating this issue.

    2. August 13, 2026 at 4:02 PM UTCidentified

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

    3. August 13, 2026 at 4:02 PM UTCmonitoring

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

    4. August 13, 2026 at 4:51 PM UTCresolved

      This incident has been resolved.

    PR Notifications delayed

    Started July 26, 2026 at 2:30 AM UTC · 0m

    IssuesMinor incident
    1. July 26, 2026 at 5:02 AM UTCresolved

      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.

    Upload processing is severely delayed

    Started July 22, 2026 at 3:02 PM UTC · 5h 58m

    OutageMajor incident
    Affected components
    Codecov Backend
    1. July 22, 2026 at 4:36 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 22, 2026 at 4:57 PM UTCinvestigating

      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.

    3. July 22, 2026 at 6:12 PM UTCidentified

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

    4. July 22, 2026 at 7:34 PM UTCidentified

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

    5. July 22, 2026 at 7:39 PM UTCidentified

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

    6. July 22, 2026 at 8:05 PM UTCmonitoring

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

    7. July 22, 2026 at 8:17 PM UTCmonitoring

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

    8. July 22, 2026 at 8:37 PM UTCmonitoring

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

    9. July 22, 2026 at 9:00 PM UTCresolved

      This incident has been resolved.

    Codecov services partially impacted and causing slowdowns

    Started July 16, 2026 at 4:42 PM UTC · 12h 47m

    IssuesMinor incident
    1. July 16, 2026 at 4:42 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 16, 2026 at 4:48 PM UTCidentified

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

    3. July 16, 2026 at 7:59 PM UTCmonitoring

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

    4. July 17, 2026 at 5:29 AM UTCresolved

      This incident has been resolved.

    Degraded processing service

    Started July 15, 2026 at 5:29 PM UTC · 6h 55m

    OutageMajor incident
    1. July 15, 2026 at 5:29 PM UTCinvestigating

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

    2. July 15, 2026 at 5:30 PM UTCidentified

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

    3. July 15, 2026 at 5:30 PM UTCmonitoring

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

    4. July 16, 2026 at 12:24 AM UTCresolved

      This incident has been resolved.

    Codecov UI showing 400 Bad Request

    Started July 8, 2026 at 3:42 PM UTC · 3h 3m

    IssuesMinor incident
    Affected components
    Codecov Frontend
    1. July 8, 2026 at 3:42 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 8, 2026 at 3:43 PM UTCidentified

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

    3. July 8, 2026 at 4:12 PM UTCmonitoring

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

    4. July 8, 2026 at 6:45 PM UTCresolved

      This incident has been resolved.

    Codecov uploaders (Action/Orb/Step) fail gpg verification

    Started June 6, 2026 at 1:00 PM UTC · 0m

    Pending
    1. June 10, 2026 at 3:22 AM UTCresolved

      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.

    Integrity verification on the CLI/Action is failing and blocking uploads to Codecov

    Started April 23, 2026 at 2:13 PM UTC · 20m

    IssuesMinor incident
    1. April 23, 2026 at 2:13 PM UTCinvestigating

      We are currently investigating the issue.

    2. April 23, 2026 at 2:15 PM UTCidentified

      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. April 23, 2026 at 2:15 PM UTCmonitoring

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

    4. April 23, 2026 at 2:33 PM UTCresolved

      This incident has been resolved.

    Notifications might be delayed

    Started April 15, 2026 at 4:27 PM UTC · 48m

    Pending
    Affected components
    Codecov Backend
    1. April 15, 2026 at 4:27 PM UTCinvestigating

      We are currently investigating this issue.

    2. April 15, 2026 at 5:15 PM UTCresolved

      This incident has been resolved.

    Coverage notifications delayed

    Started March 22, 2026 at 2:07 PM UTC · 16h 56m

    OutageMajor incident
    1. March 22, 2026 at 2:07 PM UTCinvestigating

      We are currently investigating the issue.

    2. March 22, 2026 at 7:25 PM UTCidentified

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

    3. March 22, 2026 at 8:08 PM UTCmonitoring

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

    4. March 23, 2026 at 7:03 AM UTCresolved

      This incident has been resolved.

    Coverage notifications delayed

    Started March 20, 2026 at 8:57 PM UTC · 7h 8m

    IssuesMinor incident
    Affected components
    Codecov Backend
    1. March 20, 2026 at 8:57 PM UTCinvestigating

      We are currently investigating this issue.

    2. March 21, 2026 at 4:05 AM UTCresolved

      This incident has been resolved.

    Coverage notifications delayed

    Started March 19, 2026 at 7:22 PM UTC · 1d 0h

    Pending
    Affected components
    Codecov Backend
    1. March 19, 2026 at 7:22 PM UTCinvestigating

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

    2. March 19, 2026 at 7:23 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results

    3. March 20, 2026 at 7:53 AM UTCmonitoring

      We are continuing to monitor for any further issues.

    4. March 20, 2026 at 7:30 PM UTCresolved

      This incident has been resolved.

    Unable to login with Bitbucket

    Started March 16, 2026 at 11:46 AM UTC · 1d 4h

    OutageMajor incident
    Affected components
    Codecov Frontend
    1. March 16, 2026 at 11:46 AM UTCinvestigating

      With identified an issue with our OAuth connection for Bitbucket

    2. March 17, 2026 at 2:06 PM UTCmonitoring

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

    3. March 17, 2026 at 4:07 PM UTCresolved

      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.

    Upload Processing Queue Slowdown

    Started March 10, 2026 at 9:44 PM UTC · 4h 58m

    IssuesMinor incident
    Affected components
    Codecov Backend
    1. March 10, 2026 at 9:44 PM UTCinvestigating

      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. March 11, 2026 at 2:42 AM UTCresolved

      This incident has been resolved.

    Upload Processing Queue Slowdown

    Started February 26, 2026 at 9:20 PM UTC · 10h 36m

    OutageMajor incident
    Affected components
    Codecov Backend
    1. February 26, 2026 at 9:20 PM UTCinvestigating

      We are currently investigating this issue.

    2. February 26, 2026 at 10:39 PM UTCidentified

      We have identified the issue and are deploying a fix.

    3. February 26, 2026 at 11:47 PM UTCinvestigating

      We are continuing to investigate this issue.

    4. February 27, 2026 at 12:27 AM UTCidentified

      We have identified a solution and are deploying a fix.

    5. February 27, 2026 at 12:39 AM UTCmonitoring

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

    6. February 27, 2026 at 1:12 AM UTCmonitoring

      We are continuing to monitor for any further issues.

    7. February 27, 2026 at 7:56 AM UTCresolved

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

    Upload Processing Queue Slowdown

    Started February 19, 2026 at 3:00 AM UTC · 0m

    OutageMajor incident
    1. February 26, 2026 at 5:16 PM UTCresolved

      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.

    Slower Processing Bundle Analysis

    Started December 9, 2025 at 8:54 AM UTC · 2d 5h

    Pending
    Affected components
    Codecov Backend
    1. December 9, 2025 at 8:54 AM UTCmonitoring

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

    2. December 11, 2025 at 2:42 PM UTCresolved

      This incident has been resolved.

    Slower processing

    Started November 18, 2025 at 7:14 PM UTC · 21h 4m

    Pending
    Affected components
    Codecov Backend
    1. November 18, 2025 at 7:14 PM UTCinvestigating

      We are currently investigating this issue.

    2. November 18, 2025 at 8:30 PM UTCmonitoring

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

    3. November 19, 2025 at 4:18 PM UTCresolved

      This incident has been resolved.

    Cli uploader download issues

    Started November 18, 2025 at 2:33 PM UTC · 3h 27m

    OutageMajor incident
    1. November 18, 2025 at 2:33 PM UTCinvestigating

      Cloudflare is having issues and that impacts the codecov cli

    2. November 18, 2025 at 5:59 PM UTCresolved

      This incident has been resolved.