Snyk Tests for Gradle projects Degradation

What to do

• Check whether you use Snyk Snyk Open Source, Snyk Open Source in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d 10h it lasted.

  Anything that failed between 2026-05-22 02:29 UTC and 2026-05-26 13:20 UTC may need a replay.

• Subscribe to Snyk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 4

1. identifiedMay 22, 2026, 2: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.

   provider

2. identifiedMay 22, 2026, 2: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.

   provider

3. monitoringMay 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.

   provider

4. resolvedMay 26, 2026, 1:20 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.