All affected Bitbucket Cloud integrations were identified, and their users received instructions to authorize them again. Integrations that were authorized again work normally.
The root cause was a Bitbucket service error on October 27, 2026, at 03:45 UTC, which invalidated the credentials of some integrations. We shared the details with Atlassian for their investigation.
Resolved
All affected Bitbucket Cloud integrations were identified, and their users received instructions to authorize them again. Integrations that were authorized again work normally.
The root cause was a Bitbucket service error on October 27, 2026, at 03:45 UTC, which invalidated the credentials of some integrations. We shared the details with Atlassian for their investigation.
Monitoring
We identified every affected integration and are now contacting their users directly. An integration starts to work again as soon as its user authorizes it again in the Cycode console under [Settings > Integrations > Bitbucket]. We reported the Bitbucket error to Atlassian and will post an update when we have more information.
Investigating
Summary
Some Bitbucket Cloud integrations that use OAuth disconnected after Bitbucket’s authentication service returned errors on October 27, 2026, at 03:45 UTC.
Impact
For affected integrations, Cycode cannot access Bitbucket. Scans, repository syncs, and commit statuses for those workspaces stop until the integration is authorized again. Integrations that use app passwords, API tokens, or workspace access tokens are not affected.
Latest update
Our investigation shows that Bitbucket issued new credentials for these integrations but did not deliver them to Cycode, because its service returned an error. Bitbucket no longer accepts the previous credentials, so the integrations cannot recover automatically. We are reporting the issue to Atlassian.
Action required
If your Bitbucket integration shows as disconnected, authorize it again in the Cycode console under [Settings > Integrations > Bitbucket]. Cycode continues from where it stopped, and no other change is necessary.
We will post an update when we have more information.