outages.live
Live
CodecovIncident ·

Minor Service Outage

ResolvedOfficial update
0

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

State

Resolved

Started

Lasted

42 min

Worst impact

Degraded

Timeline

2 updates
16:0916:1916:3016:4016:51
DegradedUpdate postedTimes in UTC

Components degraded

42 min 100%

Updates

Times in UTC

As posted by Codecov

Resolved
Components degraded

Affected components

2
GitHub ActionsGitHub Webhooks

Codecov in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

4

Median duration

1 h 42 min

This incident

59% 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 42 min
90 days agoToday

Other Codecov incidents

All incidents

Codecov·Partially Degraded Service

Codecov reports that the GitHub Actions component had degraded service. Codecov reports that the incident is resolved. The outage lasted 114 minutes.

Resolved

Codecov·Partially Degraded Service

Codecov reports a partially degraded service for GitHub Git Operations. Codecov says the incident is resolved. It lasted 102 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.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