Codecov reported "Partially Degraded Service" on its status page at 2026-11-13 16:03 UTC. Codecov reports a service outage. GitHub Pull Requests is degraded. Codecov is investigating the problem.

Codecov lists these components: GitHub Pull Requests.

When did the incident start and end?

It started at 2026-11-13 16:03 UTC. This page shows the end time when Codecov marks it resolved.

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

DegradedOfficial update

Codecov reports a service outage. GitHub Pull Requests is degraded. Codecov is investigating the problem.

State

Components degraded

Started

Ongoing for

47 min

Worst impact

Degraded

Timeline

1 update

16:0316:1516:2616:3816:50

DegradedUpdate postedTimes in UTC

Components degraded

47 min 100%

Updates

Times in UTC

As posted by Codecov

Components degraded

Affected components

GitHub Pull Requests

Codecov in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

36 min

This incident

1.3× the median

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

2 h 23 min

median 36 min

90 days agoToday

Other Codecov incidents

All incidents

Codecov·Partially Degraded Service

Codecov reports a partially degraded service that affects GitHub Webhooks. Codecov says the incident is resolved. The incident lasted 36 minutes.

Resolved

Codecov·Partial System Outage

Codecov reports a partial outage that affects GitHub Actions and GitHub Webhooks. Codecov resolved this incident. The outage lasted 33 minutes.

Resolved

Codecov·Partially Degraded Service

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

Resolved

Codecov·Partially Degraded Service

Codecov reports a partial outage that affects GitHub Pull Requests. Codecov resolved the incident after 2 hours.

Resolved

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

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