Snyk incident

Snyk BitBucket Server Broker Integrations Degraded

Minor Resolved View vendor source →

Snyk experienced a minor incident on January 21, 2026 affecting Snyk Code and Snyk Code and 1 more component, lasting 1d 18h. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 01:48 PM UTC
Resolved
Jan 23, 2026, 08:02 AM UTC
Duration
1d 18h
Detected by Pingoru
Jan 21, 2026, 01:48 PM UTC

Affected components

Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk Container

Update timeline

  1. investigating Jan 21, 2026, 01:48 PM UTC

    We are currently investigating degradation affecting BitBucket Server Brokered integrations. This degradation specifically affects Universal Broker versions 4.218.0 through 5.4.8. Customers may experience failures across the PR Experience, including PR Checks, fixed PRs, and inline comments. The Snyk Incident Response has been invoked, and investigations are underway.

  2. monitoring Jan 21, 2026, 03:13 PM UTC

    Following our investigation, we have determined that Universal Broker version 5.4.9 contains a resolution for this issue. We recommend that affected customers upgrade to version 5.4.9 or, preferably, the latest available release to restore full service and maintain ongoing stability.

  3. resolved Jan 23, 2026, 08:02 AM UTC

    All affected customers should upgrade to Universal Broker version 5.4.9 to restore service. The Snyk Incident Response has now been stood down.