Bitbucket Cloud API Token Authentication Failures

Our Engineers have now deployed the fix to all Snyk environments, resolving the incident.

The Snyk Incident Response has now been stood down.

Snyk engineers have implemented a fix in the UI for SNYK-US-02, resolving the issue in that environment. Snyk plans to deploy this fix to the other environments tomorrow, October 3rd.

While we have addressed the root issue, customers cannot configure Bitbucket Cloud integrations unless they have a pre-existing App Password.

Our teams are actively working towards restoring API Token integration functionality.

Although we have taken steps to resolve the underlying fault, customers will not be able to set up Bitbucket Cloud integrations unless they have a pre-existing App Password.

Our Engineers are working on a fix for this outstanding issue.

Snyk engineers have completed mitigation steps in all environments and are currently monitoring the situation.

Snyk Engineers continue their mitigation efforts. Additional updates forthcoming.

Customers who set up or migrated their Bitbucket Cloud token integrations to use API Token authentication instead of App Password authentication on or after September 23 at 3 p.m. UTC are experiencing failures when executing Git operations.

The Snyk Incident Response is currently underway. Snyk engineers have identified the issue and are taking steps to mitigate its impact.