outages.live
Live

Codecov

Codecov is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

1 h 36 min

Longest incident

2 h 23 min

Components

18
Codecov Frontend Operational
90 days ago1 day with an incidentToday
Codecov Backend Operational
90 days ago2 days with an incidentToday
GitLab Operational
90 days agoNo incidentsToday
Codecov Billing (Stripe API) Operational
90 days agoNo incidentsToday
Codecov Docs (hosted by ReadMe) Operational
90 days agoNo incidentsToday

GCP

Google Cloud Platform SQL Operational
90 days agoNo incidentsToday
Google Cloud Platform Kubernetes Engine Operational
90 days agoNo incidentsToday
Google Cloud Platform Cloud Storage Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Container Engine Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Compute Engine Operational
90 days agoNo incidentsToday

Github

GitHub Actions Operational
90 days agoNo incidentsToday
GitHub API Requests Operational
90 days agoNo incidentsToday
GitHub Git Operations Operational
90 days agoNo incidentsToday
GitHub Pull Requests Operational
90 days agoNo incidentsToday
GitHub Webhooks Operational
90 days agoNo incidentsToday

Bitbucket

Atlassian Bitbucket API Operational
90 days agoNo incidentsToday
Atlassian Bitbucket Pipelines Operational
90 days agoNo incidentsToday
Atlassian Bitbucket Webhooks Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 5, 2026

Duration2 h 23 min06:53 to 09:15Codecov app and services are downMajor outage

This incident has been resolved.

Aug 13, 2026

Duration50 min16:01 to 16:51Degraded performance on report processingDegraded

This incident has been 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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane