outages.live
Live
CodecovIncident · 2026-10-05 06:53 UTC

Codecov app and services are down

ResolvedOfficial update

This incident has been resolved.

The latest update from Codecov.

State

Resolved

Started

28 d ago

2026-10-05 06:53 UTC

Lasted

2 h 23 min

until 2026-10-05 09:15 UTC

Worst impact

Major outage

Timeline

13 updates
06:5307:2808:0408:4009:15
Major outageUpdate postedTimes in UTC

Investigating

3 min 2%

Identified

1 h 38 min 69%

Monitoring

42 min 30%

Updates

Times in UTC

As posted by Codecov

Resolved2026-10-05 09:15 UTC

This incident has been resolved.

Monitoring2026-10-05 09:03 UTC

We are continuing to monitor for any further issues.

Monitoring2026-10-05 09:02 UTC

We are continuing to monitor for any further issues.

Monitoring2026-10-05 08:33 UTC

We are continuing to monitor for any further issues.

Monitoring2026-10-05 08:33 UTC

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

Identified2026-10-05 08:24 UTC

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

Identified2026-10-05 08:09 UTC

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

Identified2026-10-05 07:45 UTC

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

Identified2026-10-05 07:25 UTC

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

Identified2026-10-05 07:11 UTC

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

Identified2026-10-05 06:55 UTC

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

Investigating2026-10-05 06:54 UTC

We are continuing to investigate the issue

Investigating2026-10-05 06:53 UTC

We are currently investigating this issue.

Affected components

2
Codecov FrontendCodecov Backend

Codecov in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

1 h 36 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 23 min
median 1 h 36 min
90 days agoToday

Other Codecov incidents

All incidents

Codecov·Degraded performance on report processing

This incident has been resolved.

Resolvedresolved 80 d ago

Follow Codecov

Your coding agent knows when Codecov is down, and tells you when a failure is theirs, not yours. You can also get Codecov incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "codecov" and tell me if Codecov has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=codecov
Slack
/feed subscribe https://outages.cc/feed.xml?providers=codecov

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane