Snyk incident

BitBucket Cloud Integrations Degraded

Resolved after 3 hours 31 minutes, affecting Snyk Code and Snyk Code and 1 more, on October 29, 2026.

resolved Oct 29, 2026, 02:16 PM UTC

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.

Started
Oct 29, 2026, 10:44 AM UTC
Resolved
Oct 29, 2026, 02:16 PM UTC
Duration
3h 31m
Detected by Pingoru
Oct 29, 2026, 10:44 AM UTC

Affected components

Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaC

Update timeline

  1. investigating Oct 29, 2026, 10:44 AM UTC

    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. monitoring Oct 29, 2026, 12:25 PM UTC

    Our Engineers have implemented a fix, and we're observing improvements in success rates. We are now monitoring to ensure services remain stable.

  3. resolved Oct 29, 2026, 02:16 PM UTC

    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.

Your product runs on more than Snyk

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →