Description
Describe the bug
Since April 20, 2026, private repositories have stopped working.
Initially, logging in via Bitbucket was failing. it either caused an infinite redirect or returned a 500 error. Eventually, login started working again, but private repositories within organizations are no longer visible.
I can still see my personal private repositories, but organization private repositories do not appear. Public repositories are visible as expected.
The "Sync" button does not trigger any action.
When I try to open a repository directly (e.g., https://app.codecov.io/bb/tallink/central-config-server), I get the following error:
Not found
To view private repositories ensure you are logged in, you can also check on Codecov's status:
https://status.codecov.io/
or see our docs:
https://docs.codecov.io/
Error 404
I am a member of the organization, and network requests confirm that the API recognizes my membership in "tallink".
I also tested with other organizations I belong to, and the issue persists across all of them.
Expected behavior
Private repositories to show up in https://app.codecov.io/bb/{org_name}
Screenshots
Additional context
Add any other context about the problem here.
Activity
linear commentedon Apr 22, 2026
CCMRG-2174
ownede commentedon Apr 22, 2026
Having the same issue, can't access my repos from codecov, I also don't see PR comments being added while submitting the changes via CI.
konstantin-nesterov commentedon Apr 22, 2026
We are seeing the same symptom on our Bitbucket workspace since ~Apr 22, 2026 — every repository returns 404 in the UI, "Sync" does nothing, PR comments stop showing up. Dropping some extra evidence that points at a likely root cause, in case it helps.
What we see on the API side
Using a workspace-level Codecov API token, probing Codecov's REST v2 directly:
Coverage uploads keep returning HTTP 200, so data still reaches Codecov — it just isn't surfaced anywhere.
Our hypothesis: Atlassian CHANGE-2770
HTTP 410with a payload of"Bitbucket API: Gone"is exactly what Bitbucket Cloud started returning for the cross-workspace REST APIs, whose final removal landed on Apr 14, 2026:Other integrators had to migrate off the same endpoints — e.g. Renovate (renovatebot/renovate#42102) and GitLab (https://gitlab.com/gitlab-org/gitlab/-/issues/589153). The replacement is
GET /2.0/user/workspaces+GET /2.0/repositories/{workspace}instead ofGET /2.0/repositories?role=....Pattern of what's broken vs what still works matches this perfectly:
/upload/v4)Heads-up: a second Atlassian change is coming May 4
While on this topic — a related deprecation is rolling out now:
client_credentialsgrants no longer return arefresh_token, all token-authenticated requests must go toapi.bitbucket.org(notwww.bitbucket.org), and a few auth patterns stop being accepted.If Codecov's Bitbucket OAuth flow still relies on any of those, we might get a second wave of breakage on May 4 — worth looking at together.
Asks
Happy to run further diagnostic calls against our workspace if it helps narrow things down.
ScarletKuro commentedon Apr 22, 2026
Hopping that maybe someone with Pro support can escalate this and point to to this issue?
ScarletKuro commentedon Apr 24, 2026
Today at 8:00 UTC time I started to see private repos again, a hour ago it wasn't working.
ownede commentedon Apr 30, 2026
As for today, Codecov posts comments to my BB repo, but I'm not able to see my repos on codecov ._.
ScarletKuro commentedon May 1, 2026
Hmmm weird, I can see all my repos