Snyk incident

Snyk Tests for Gradle projects Degradation

Minor Resolved View vendor source →

Snyk experienced a minor incident on May 22, 2026 affecting Snyk Open Source and Snyk Open Source, lasting 4d 10h. The incident has been resolved; the full update timeline is below.

Started
May 22, 2026, 02:29 AM UTC
Resolved
May 26, 2026, 01:20 PM UTC
Duration
4d 10h
Detected by Pingoru
May 22, 2026, 02:29 AM UTC

Affected components

Snyk Open SourceSnyk Open Source

Update timeline

  1. identified May 22, 2026, 02:29 AM UTC

    Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks. The investigation is ongoing under the Snyk Incident Response process.

  2. identified May 22, 2026, 02:52 PM UTC

    Our Engineers have confirmed that the US-01 (app.snyk.io) environment has shown no further degradation following re-deployment and appears to be stable. Investigation into the AU-01 (app.au.snyk.io) environment is still ongoing, and we will provide a further update as we progress.

  3. monitoring May 25, 2026, 11:26 PM UTC

    Our Engineers have implemented a fix, and we're no longer observing the degradation on the AU-01 (app.au.snyk.io) environment. We will continue to monitor for ongoing stability.

  4. resolved May 26, 2026, 01:20 PM UTC

    We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.