Codecov lists these components: GitHub Actions.

When did the incident start and end?

It started at 2026-11-04 17:45 UTC and ended at 2026-11-04 18:15 UTC. It lasted 30 min.

How do I get alerts for Codecov?

Subscribe to the Codecov live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Codecov. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CodecovIncident ·

Minor Service Outage

Q: What happened?

Codecov reported "Minor Service Outage" on its status page at 2026-11-04 17:45 UTC. Codecov reported a minor service outage that affected GitHub Actions. Codecov resolved the outage. The outage lasted 30 minutes, from 17:45 to 18:15 UTC.

ResolvedOfficial update

Codecov reported a minor service outage that affected GitHub Actions. Codecov resolved the outage. The outage lasted 30 minutes, from 17:45 to 18:15 UTC.

State

Resolved

Started

Lasted

30 min

Worst impact

Degraded

Timeline

2 updates

17:4517:5218:0018:0718:15

DegradedUpdate postedTimes in UTC

Components degraded

30 min 100%

Updates

Times in UTC

As posted by Codecov

Resolved

Components degraded

Affected components

GitHub Actions

Codecov in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 16 min

This incident

60% shorter than 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 16 min

90 days agoToday

Other Codecov incidents

All incidents

Codecov·Minor Service Outage

Codecov reported a minor service outage that affected GitHub Actions and GitHub Webhooks. Codecov reports that the outage is resolved. It lasted 42 minutes.

Resolved

Codecov·Partially Degraded Service

Codecov reports a partially degraded service that affects GitHub Actions. Codecov reports that the incident is resolved. The incident lasted 114 minutes.

Resolved

Codecov·Partially Degraded Service

Codecov reports degraded service for GitHub Git Operations. Codecov resolved the incident. The incident lasted 1 hour and 42 minutes.

Resolved

Codecov·Codecov app and services are down

This incident has been resolved.

Resolved

Codecov·Degraded performance on report processing

This incident has been resolved.

Resolved

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