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.
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: 7 incidents · 364 of 365 days with none posted · 11h 53m 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%
Downtime like this can be refundable
If you're a paying Codecov customer, outages in these windows may count against Codecov's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
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.
Time to resolve, from Codecov's own incident posts (1 year)
Median time to resolve
6h 55m
Slowest 10% take longer than
16h 59m
From 7 incidents Codecov published and resolved in the last 1 year, 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.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is Codecov currently down?
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.
Codecov's last resolved incident started 18 days ago and lasted 59 minutes (degraded performance).
›What's Codecov's 30-day uptime?
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.
›How do I monitor Codecov in production?
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).
›How does CheckUpstream track Codecov?
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.