Major incident

Snyk: BitBucket Cloud Integrations Degraded

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk API & Web, Snyk Secrets

Current status of Snyk: Operational — live Snyk status

Timeline

1. Oct 29, 2026, 10:44 UTC
   investigating
   We are investigating degradation affecting Bitbucket Cloud integrations across all Snyk environments. Customers may observe that their Bitbucket Cloud integrations are showing the error 'could not connect'. This will affect all Bitbucket Cloud actions, such as PR Checks, Importing and Recurring Tests, among others. The Snyk Incident Response has been invoked.
2. Oct 29, 2026, 12:25 UTC
   monitoring
   Our Engineers have implemented a fix, and we're observing improvements in success rates. We are now monitoring to ensure services remain stable.
3. Oct 29, 2026, 14:16 UTC
   resolved
   Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.

Updates as published by Snyk (original).