">
sevanalysis

Codecov

Apps and SaaS. Source: Codecov status page.

Incidents, last 90 days
3
Median to mitigation
1m
Median to resolution
50m
p95 to resolution
2h 23m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

Login, tokens, certificates or credentials failed1
The text does not say enough to tell1
Exhausted memory, disk, CPU, queues, connection pools or quotas1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

All recorded incidents

Codecov app and services are down critical 2026-10-05 06:53 UTC 2h 23m

Affected: Codecov Frontend, Codecov Backend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate the issue

  3. identified

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

  4. identified

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

  5. identified

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

  6. identified

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

  7. identified

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

  8. identified

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

  9. monitoring

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

  10. monitoring

    We are continuing to monitor for any further issues.

  11. monitoring

    We are continuing to monitor for any further issues.

  12. monitoring

    We are continuing to monitor for any further issues.

  13. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded performance on report processing minor 2026-08-13 16:01 UTC 50m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. identified

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

  3. monitoring

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

PR Notifications delayed minor 2026-07-26 02:30 UTC 0m

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. resolved

    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.

Excerpts are shortened. Read the full incident on Codecov's status page.

Upload processing is severely delayed major 2026-07-22 15:02 UTC 5h 58m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. identified

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

  3. monitoring

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

  4. investigating

    We are currently investigating this issue.

  5. investigating

    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

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

  7. identified

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

  8. identified

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

  9. monitoring

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

  10. monitoring

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

  11. monitoring

    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

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Codecov services partially impacted and causing slowdowns minor 2026-07-16 16:42 UTC 12h 47m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. identified

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

  3. monitoring

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded processing service major 2026-07-15 17:29 UTC 6h 55m

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. identified

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

  3. monitoring

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Codecov UI showing 400 Bad Request minor 2026-07-08 15:42 UTC 3h 3m

Affected: Codecov Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. identified

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

  3. monitoring

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Codecov uploaders (Action/Orb/Step) fail gpg verification none 2026-06-06 13:00 UTC 0m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

  1. resolved

    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...

Excerpts are shortened. Read the full incident on Codecov's status page.

Integrity verification on the CLI/Action is failing and blocking uploads to Codecov minor 2026-04-23 14:13 UTC 20m

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating the issue.

  2. identified

    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

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Notifications might be delayed none 2026-04-15 16:27 UTC 48m

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Coverage notifications delayed major 2026-03-22 14:07 UTC 16h 56m

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating the issue.

  2. identified

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

  3. monitoring

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Coverage notifications delayed minor 2026-03-20 20:57 UTC 7h 8m

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Coverage notifications delayed none 2026-03-19 19:22 UTC 24h 8m

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

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

  2. monitoring

    A fix has been implemented and we are monitoring the results

  3. monitoring

    We are continuing to monitor for any further issues.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Unable to login with Bitbucket major 2026-03-16 11:46 UTC 28h 21m

Affected: Codecov Frontend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    With identified an issue with our OAuth connection for Bitbucket

  2. monitoring

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

  3. resolved

    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.

Excerpts are shortened. Read the full incident on Codecov's status page.

Upload Processing Queue Slowdown minor 2026-03-10 21:44 UTC 4h 58m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    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

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Upload Processing Queue Slowdown major 2026-02-26 21:20 UTC 10h 36m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate this issue.

  3. identified

    We have identified the issue and are deploying a fix.

  4. investigating

    We are continuing to investigate this issue.

  5. identified

    We have identified a solution and are deploying a fix.

  6. monitoring

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

  7. monitoring

    We are continuing to monitor for any further issues.

  8. resolved

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

Excerpts are shortened. Read the full incident on Codecov's status page.

Upload Processing Queue Slowdown major 2026-02-19 03:00 UTC 0m

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. resolved

    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...

Excerpts are shortened. Read the full incident on Codecov's status page.

Slower Processing Bundle Analysis none 2025-12-09 08:54 UTC 2d 5h

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. monitoring

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

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Slower processing none 2025-11-18 19:14 UTC 21h 4m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Cli uploader download issues major 2025-11-18 14:33 UTC 3h 27m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

  1. investigating

    Cloudflare is having issues and that impacts the codecov cli

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Login to Codecov via Sentry button degraded none 2025-10-30 13:40 UTC 31m

Affected: Codecov Frontend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Codecov AI Commands none 2025-10-14 16:34 UTC 27h 29m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Test Analytics are down minor 2025-10-09 01:00 UTC 6d

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    Test Analytics are down

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

SSL issue none 2025-09-02 17:59 UTC 2h 38m

Affected: Codecov Frontend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Generalized latency issues throughout infrastructure none 2025-06-12 18:37 UTC 2h 25m

Affected: Codecov Backend

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

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

  2. identified

    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

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Extended Queue Processing Times none 2025-05-14 08:00 UTC 0m

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. resolved

    We are experiencing backups in our processing queues. This creates delays when processing coverage and test report upload files. This issue lasted from: 2025-05-14 8:00UTC to 2025-05-14 18:00UTC and has been fully resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Queue Slowdown none 2025-05-13 18:44 UTC 10h 45m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. identified

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

  3. identified

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Queue Slowdown minor 2025-05-12 09:45 UTC 17h 47m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. monitoring

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

  2. monitoring

    We are continuing to monitor for any further issues.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Test Analytics Outage major 2025-05-02 00:07 UTC 32m

Affected: Codecov Frontend, Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. identified

    We are currently experiencing downtime with Test Analytics. This issue began at 2025-05-01 22:03 UTC. We have identified the issue and are working toward resolution.

  2. resolved

    This incident is resolved and Test Analytics is fully operational

Excerpts are shortened. Read the full incident on Codecov's status page.

System Degraded none 2025-03-12 17:28 UTC 23m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Slower processing minor 2025-03-10 19:37 UTC 2h 34m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Slack Notification issues minor 2025-02-26 17:51 UTC 9h 23m

Affected: Codecov Frontend, Codecov Backend

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are currently experiencing issues with sending notifications to Slack due to an ongoing incident: https://slack-status.com/2025-02/1b757d1d0f444c34

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded Performance none 2025-02-03 16:03 UTC 2h 32m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Error processing uploads using the global upload token none 2025-01-28 17:00 UTC 0m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. resolved

    On 28 January from 12:00 to 30 January 13:00 EST There was a disruption to global upload token validation that resulted in the Codecov system accepting uploads but internally denying the upload. This resulted in failed upload processing for repositories configured to use the...

Excerpts are shortened. Read the full incident on Codecov's status page.

Queue backup resulting in delayed reporting none 2025-01-16 18:58 UTC 2h 52m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded UI none 2025-01-15 14:26 UTC 1h 49m

Affected: Codecov Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Unable to login to Codecov major 2025-01-15 00:45 UTC 13h 18m

Affected: Codecov Frontend, Codecov Backend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    It looks like uploads are unaffected, user are not able to login to Codecov using any service at this time. We are investigating.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Delayed notifications minor 2025-01-09 20:24 UTC 2h 16m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are experiencing high volumes and are seeing some queue back ups resulting in longer than normal notification times.

  2. monitoring

    Queue levels are approaching normal. Notification times should be back to normal as well.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Intermittent CLI Verification Issues minor 2025-01-08 21:40 UTC 2h 20m

Affected: Codecov Backend

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are having a problem with CLI distribution related to our caching layer. The cache is now bypassed and the issue is being investigated. This will have resulted in unexpected CLI verification failures when downloading/verifying the Codecov CLI.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Delays with Report Processing minor 2024-12-03 18:18 UTC 4h 19m

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Delays with Report Processing none 2024-11-26 18:44 UTC 2h 16m

Affected: Codecov Backend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Delays with Report Processing minor 2024-10-29 00:57 UTC 3h 21m

Affected: Codecov Backend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    Report processing is delayed. We are currently investigating the issue.

  2. identified

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

  3. resolved

    A large backlog of reports caused the system to lag behind processing. This has been remedied and the system is now fully operational.

Excerpts are shortened. Read the full incident on Codecov's status page.

UI is not operational none 2024-10-07 18:14 UTC 3m

Affected: Codecov Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. identified

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

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Reports failing major 2024-09-18 12:52 UTC 0m

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. resolved

    From ~8:30 UTC - ~12:00 UTC Codecov failed to process reports. These reports will need to be uploaded again.

Excerpts are shortened. Read the full incident on Codecov's status page.

intermittent failures for uploads minor 2024-08-16 19:00 UTC 8h 58m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Uploads are failing critical 2024-07-15 13:45 UTC 11m

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate this issue.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Unable to login or very slow none 2024-06-12 14:04 UTC 3h 47m

Affected: Codecov Frontend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. identified

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

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded performance minor 2024-04-17 20:06 UTC 3h 10m

Affected: Codecov Frontend, Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded performance minor 2024-04-17 16:10 UTC 3h

Affected: Codecov Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    Intermittent 50X errors. We are looking into it.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Codecov's status page.

Degraded Performance none 2024-04-16 19:00 UTC 0m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. resolved

    Intermittent 50X errors. We have mitigated the issue and are continuing to monitor.

Excerpts are shortened. Read the full incident on Codecov's status page.