Bitbucket Repository Cloning and OAuth Connection Unavailable

Incident Report for Fluid Attacks

Identified

Since October 29 at 18:57 GMT-05:00, repositories connected through Bitbucket OAuth credentials cannot be cloned, and their cloning status shows “Invalid credentials, access could not be granted prior to the cloning task”. Adding or re-authorizing Bitbucket OAuth credentials from the Credentials section of the organization also fails, with the Bitbucket error “Invalid client_id”. Repositories that use HTTPS or SSH credentials, or other providers (GitHub, GitLab, Azure DevOps), are not affected, and no data was lost or exposed. Our team is working on a fix.
Posted Nov 03, 2026 - 17:11 GMT-05:00
This incident affects: Platform and Cloning.