Codecov reported "Partially Degraded Service" on its status page at 2026-11-08 11:27 UTC. Codecov reports degraded GitHub API Requests. Codecov resolved this incident. The degradation lasted 36 minutes.

Codecov lists these components: GitHub API Requests.

When did the incident start and end?

It started at 2026-11-08 11:27 UTC and ended at 2026-11-08 12:03 UTC. It lasted 36 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 ·

Partially Degraded Service

ResolvedOfficial update

Codecov reports degraded GitHub API Requests. Codecov resolved this incident. The degradation lasted 36 minutes.

State

Resolved

Started

Lasted

36 min

Worst impact

Degraded

Timeline

2 updates

11:2711:3611:4511:5412:03

DegradedUpdate postedTimes in UTC

Components degraded

36 min 100%

Updates

Times in UTC

As posted by Codecov

Resolved

Components degraded

Affected components

GitHub API Requests

Codecov in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

46 min

This incident

22% 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 46 min

90 days agoToday

Other Codecov incidents

All incidents

Codecov·Partial System Outage

A partial outage affected Codecov GitHub Actions and GitHub Webhooks. Codecov reports that the incident is resolved. The outage lasted 27 minutes.

Resolved

Codecov·Minor Service Outage

Codecov GitHub Webhooks did not work correctly. Codecov reports that the incident is resolved. The outage lasted 102 minutes.

Resolved

Codecov·Partially Degraded Service

Codecov reported a partially degraded service for the GitHub Actions component. Codecov later reported that the incident is resolved. The incident lasted 27 minutes.

Resolved

Codecov·Minor Service Outage

Codecov reports degraded service on the GitHub Actions component. Codecov resolved this incident. The outage lasted 30 minutes.

Resolved

Codecov·Minor Service Outage

Codecov reported degraded service for GitHub Actions and GitHub Webhooks. Codecov later reported that the outage is resolved. The outage lasted 42 minutes.

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.live/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.live/feed.xml?providers=codecov

Slack

/feed subscribe https://outages.live/feed.xml?providers=codecov

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane