Codecov Outage History

21 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Codecov status99.46% uptime history

Every Recorded Codecov Incident

Codecov incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 5, 2026Codecov app and services are downThis incident has been resolved.2h 22mResolved
Aug 13, 2026Degraded performance on report processingThis incident has been resolved.49 minResolved
Aug 13, 2026Infrastructure MaintenanceThe scheduled maintenance has been completed.0 minScheduled
Jul 26, 2026PR Notifications delayedServer 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.-152 minResolved
Jul 22, 2026Upload processing is severely delayedThis incident has been resolved.5h 57mResolved
Jul 16, 2026Codecov services partially impacted and causing slowdownsThis incident has been resolved.12h 46mResolved
Jul 15, 2026Degraded processing serviceThis incident has been resolved.6h 54mResolved
Jul 8, 2026Codecov UI showing 400 Bad RequestThis incident has been resolved.3h 2mResolved
Jun 6, 2026Codecov uploaders (Action/Orb/Step) fail gpg verificationOn 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…0 minResolved
Apr 23, 2026Integrity verification on the CLI/Action is failing and blocking uploads to CodecovThis incident has been resolved.19 minResolved
Apr 15, 2026Notifications might be delayedThis incident has been resolved.48 minResolved
Mar 22, 2026Coverage notifications delayedThis incident has been resolved.16h 55mResolved
Mar 20, 2026Coverage notifications delayedThis incident has been resolved.7h 7mResolved
Mar 19, 2026Coverage notifications delayedThis incident has been resolved.24h 7mResolved
Mar 16, 2026Unable to login with BitbucketThis 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.28h 20mResolved
Mar 10, 2026Upload Processing Queue SlowdownThis incident has been resolved.4h 58mResolved
Feb 26, 2026Upload Processing Queue SlowdownThis incident has been resolved. We will continue monitoring for any changes.10h 36mResolved
Feb 19, 2026Upload Processing Queue SlowdownWe 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…0 minResolved
Dec 9, 2025Slower Processing Bundle AnalysisThis incident has been resolved.53h 47mResolved
Nov 18, 2025Slower processingThis incident has been resolved.21h 4mResolved
Nov 18, 2025Cli uploader download issuesThis incident has been resolved.3h 26mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Codecov incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Codecov Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Codecov acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Codecov outage in this window ran 2d 5h, against a mean recovery of 10h 10m. If you depend on Codecov in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.