CheckUpstream does not yet run an independent probe against Codecov, so no availability figure is published for it — only Codecov's own disclosure record below. 8 incidents were recorded in the past 12 months; the most recent resolved 18 days ago after 59 minutes. Status signals are polled from Codecov's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Codecov yet, so we publish no availability figure for it. What follows is Codecov's own disclosure record, which is a different thing.
Vendor disclosed: 5 incidents · 90 of 90 days with none posted · 0m of declared impact
Fewer incidents in the last 30 days than 45% of 232 tracked services.
Share of each window with no impact declared by Codecov
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.725%
1y
99.864%
Does Codecov actually matter to you?
A Codecov outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 5 incidents Codecov published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Codecov takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 13, 16:01 UTC · resolved in 59m · Resolved
Jul 22, 15:02 UTC · resolved in 7h 7m · Resolved
Jul 16, 16:42 UTC · resolved in 12h 52m · Resolved
Live Codecov status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/codecov)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Codecov is currently Operational. CheckUpstream tracks Codecov in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Codecov down" view? See the Codecov Live status page.
Jul 15, 17:29 UTC · resolved in 6h 55m · Resolved
Codecov's last resolved incident started 18 days ago and lasted 59 minutes (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Codecov yet, and the only other figure available would be derived from Codecov's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Codecov to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Codecov's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.