Snyk incident

Bitbucket Cloud Degradation

Minor Resolved View vendor source →

Snyk experienced a minor incident on December 15, 2025 affecting Snyk AppRisk and Snyk AppRisk and 1 more component, lasting 2d 22h. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2025, 03:43 PM UTC
Resolved
Dec 18, 2025, 01:54 PM UTC
Duration
2d 22h
Detected by Pingoru
Dec 15, 2025, 03:43 PM UTC

Affected components

Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Container

Update timeline

  1. investigating Dec 15, 2025, 03:43 PM UTC

    Our Engineers are aware of the degradation affecting Bitbucket Cloud integrations. Some Customers who imported projects via Bitbucket Cloud between the 30th of November and the 11th of December may notice that webhooks haven't been properly installed. The Snyk Incident Response has been invoked, and we are investigating.

  2. investigating Dec 16, 2025, 11:41 AM UTC

    Our investigation into the issue remains ongoing. Customers may have noticed that webhooks were not correctly configured for projects imported from Bitbucket Cloud. This will affect actions such as test-on push, set-and-forget, pull request checks and /snyk fix, among others. As a workaround, customers can initiate a re-import of affected projects, which will install the webhook correctly and resolve the issue. We will keep you updated with our progress.

  3. resolved Dec 18, 2025, 01:54 PM UTC

    We have identified the root cause of the incident and established that this affects only a small subset of customers. We will be reaching out to those customers in due course. However, as a workaround, customers can re-import the affected projects. The Snyk Incident Response has now been stood down.