Codecov Status. Check Current Outages and Incidents

Status Provider

Home

Status

Service

Codecov components

Tracked components

Showing 1 to 21 of 21 tracked components.

Component	Status	Type	Last changed
GCP	Operational	Group	Not recorded
Github	Operational	Group	6/15/2026
Bitbucket	Operational	Group	Not recorded
Atlassian Bitbucket API	Operational	Component	Not recorded
Codecov Frontend	Operational	Component	Not recorded
GitHub Actions	Operational	Component	Not recorded
Google Cloud Platform SQL	Operational	Component	Not recorded
Atlassian Bitbucket Pipelines	Operational	Component	Not recorded
Codecov Backend	Operational	Component	Not recorded
GitHub API Requests	Operational	Component	Not recorded
Google Cloud Platform Kubernetes Engine	Operational	Component	Not recorded
Atlassian Bitbucket Webhooks	Operational	Component	Not recorded
GitHub Git Operations	Operational	Component	Not recorded
Google Cloud Platform Cloud Storage	Operational	Component	Not recorded
Google Cloud Platform Google Container Engine	Operational	Component	Not recorded
Google Cloud Platform Google Compute Engine	Operational	Component	Not recorded
GitHub Pull Requests	Operational	Component	Not recorded
GitLab GitLab does not currently offer a native integration with status page. Please refer to https://status.gitlab.com/ for live updates on their respective services.	Operational	Component	Not recorded
Codecov Billing (Stripe API)	Operational	Component	Not recorded
GitHub Webhooks	Operational	Component	6/15/2026
Codecov Docs (hosted by ReadMe)	Operational	Component	Not recorded

Recent incidents

Official incidents

Latest outages and degradations detected from the official status page.

Codecov uploaders (Action/Orb/Step) fail gpg verification

Resolved

On Saturday, June 6th, the Codecov gpg public key located at keybase.io/codecovsecurity was absent. This caused widespread outages for users uploading with the Codecov - GitHub Action - CircleCI Orb - Bitrise Step In order to quickly move and prevent further outages, the Codecov team deleted the `codecovsecurity` account and created `codecovsecops` with the same public gpg key. This key can be verified against any pre-existing CLI to prove it is the same key and also at about.codecov.io/security. The key location was updated in all of the above uploaders on the latest versions.

Jun 6, 1:00 PMResolved Jun 6, 1:00 PMNone

Integrity verification on the CLI/Action is failing and blocking uploads to Codecov

Resolved

This incident has been resolved.

Apr 23, 2:13 PMResolved Apr 23, 2:33 PMMinor

Notifications might be delayed

Resolved

This incident has been resolved.

Apr 15, 4:27 PMResolved Apr 15, 5:15 PMNoneCodecov Backend

Coverage notifications delayed

Resolved

This incident has been resolved.

Mar 22, 2:07 PMResolved Mar 23, 7:03 AMMajor

Coverage notifications delayed

Resolved

This incident has been resolved.

Mar 20, 8:57 PMResolved Mar 21, 4:05 AMMinorCodecov Backend

Coverage notifications delayed

Resolved

This incident has been resolved.

Mar 19, 7:22 PMResolved Mar 20, 7:30 PMNoneCodecov Backend

Unable to login with Bitbucket

Resolved

This incident has been resolved. All Bitbucket users will need to login to Codecov again, as their authorizations were reset. Codecov will not be able to commincate with Bitbucket until you do.

Mar 16, 11:46 AMResolved Mar 17, 4:07 PMMajorCodecov Frontend

Upload Processing Queue Slowdown

Resolved

This incident has been resolved.

Mar 10, 9:44 PMResolved Mar 11, 2:42 AMMinorCodecov Backend

Upload Processing Queue Slowdown

Resolved

This incident has been resolved. We will continue monitoring for any changes.

Feb 26, 9:20 PMResolved Feb 27, 7:56 AMMajorCodecov Backend

Upload Processing Queue Slowdown

Resolved

We have identified a backlog in our processing queues that is causing delays in coverage report processing. Uploads are still being accepted but results may take longer than expected to appear. Our team is actively working to remediate the issue. No data has been lost. *Update 2026-02-24 5PM PT* The issue has been identified and patched, we will continue to monitor for any changes.

Feb 19, 3:00 AMResolved Feb 19, 3:00 AMMajor

Recent maintenance